Delivery vehicle including an unmanned aerial vehicle loading robot

ABSTRACT

Systems and methods include UAVs that serve to assist carrier personnel by reducing the physical demands of the transportation and delivery process. A UAV generally includes a UAV chassis including an upper portion, a plurality of propulsion members configured to provide lift to the UAV chassis, and a parcel carrier configured for being selectively coupled to and removed from the UAV chassis. UAV support mechanisms are utilized to load and unload parcel carriers to the UAV chassis, and the UAV lands on and takes off from the UAV support mechanism to deliver parcels to a serviceable point. The UAV includes computing entities that interface with different systems and computing entities to send and receive various types of information.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 15/582,168, filed on Apr. 28, 2017, which claims the benefit ofU.S. Provisional Patent Application 62/329,491, filed on Apr. 29, 2016,the contents each of which are hereby incorporated by reference.

BACKGROUND

Parcel transportation between an origin and a destination istraditionally a labor-intensive process. For short distance, “local”deliveries, an item (e.g., parcel) may be transported by a deliveryperson between the origin and the destination. For example, the deliveryperson may drive a vehicle to transport the item between the origin andthe destination, and may ensure that the item is properly picked upand/or delivered according to delivery instructions. For longer-distancedeliveries, transportation of an item may involve a number of deliverypersonnel, who may individually perform one or more steps for picking upan item, sorting the item one or more times, transporting the item froma final sort location to a final delivery destination, and/or deliveringthe item from the delivery vehicle to the final destination address(e.g., serviceable point). Because of the labor-intensive nature of thisprocess, various attempts have been made to assist carrier personnel byreducing the physical demands required in the transportation anddelivery process; however, prior attempts have faced substantialdifficulties in ensuring that various aspects of the transportation anddelivery process are properly performed. For example, attempts have beenmade to utilize unmanned vehicles, such as Unmanned Aerial Vehicles(UAVs) to transport items from a final sort location to an intendeddelivery destination. However, such concepts are generally limited bythe effective range of the UAVs, as well as the number of available UAVsthat may be utilized to deliver items to locations a substantialdistance away from the final sort location.

Accordingly, a need exists for additional systems and methods to assistcarrier personnel and thereby reduce the physical demands of thetransportation and delivery process.

BRIEF SUMMARY

In one embodiment, a UAV for delivering a parcel includes a UAV chassisincluding an upper portion having a plurality of propulsion membersconfigured to provide lift to the UAV chassis. The UAV chassis furtherincludes a lower portion positioned below the upper portion in avertical direction, the lower portion defining an internal cavity. Aparcel carrier of the UAV is configured for being selectively coupled toand removed from the UAV chassis, the parcel carrier including anengagement housing configured for being at least partially insertedwithin the internal cavity of the lower portion of the UAV chassis andthereby secured to the UAV chassis. The parcel carrier has a parcelcarrying mechanism coupled to and positioned below the engagementhousing, where the parcel carrying mechanism is configured for engagingand holding the parcel.

In another embodiment, a UAV for delivering a parcel includes a UAVchassis including an upper portion including a plurality of propulsionmembers configured to provide lift to the UAV chassis. The UAV chassisfurther includes a lower portion positioned below the upper portion in avertical direction. A parcel carrier is selectively coupled to andremovable from the UAV chassis, the parcel carrier including anengagement housing configured for being secured to the lower portion ofthe UAV chassis. A parcel carrying mechanism of the parcel carrier iscoupled to the engagement housing and positioned below the engagementhousing, where the parcel carrying mechanism is configured to engage aparcel.

In yet another embodiment, a UAV for delivering a parcel includes a UAVchassis includes a plurality of propulsion members configured to providelift to the UAV chassis and a UAV electrical interface electricallycoupled to the plurality of propulsion members. The UAV further includesa parcel carrier selectively coupled to and removable from the UAVchassis, the parcel carrier including an engagement housing configuredfor being secured to the UAV chassis. The engagement housing includes acarrier electrical interface configured for being electrically coupledto the UAV electrical interface when the parcel carrier is coupled tothe UAV chassis. A parcel carrying mechanism of the parcel carrier iscoupled to the engagement housing, where the parcel carrying mechanismis configured to engage a parcel, and a power source of the parcelcarrier is electrically coupled to the carrier electrical interface andconfigured for powering the plurality of propulsion members when theparcel carrier is coupled to the UAV chassis.

In one embodiment, an enhanced parcel delivery system includes a UAVhaving a UAV chassis including an upper portion and a plurality ofpropulsion members configured to provide lift to the UAV chassis. TheUAV chassis includes a lower portion positioned below the upper portionin a vertical direction, the lower portion defining an internal cavity.A first parcel carrier is selectively coupled to and removable from theUAV chassis, the first parcel carrier including a first engagementhousing configured to be at least partially inserted within the internalcavity of the lower portion of the UAV chassis. The first parcel carrierincludes a first power source positioned within the first engagementhousing and configured to be electrically coupled to the plurality ofpropulsion members. A first parcel carrying mechanism of the firstparcel carrier is coupled to and positioned below the first engagementhousing, where the first parcel carrying mechanism is configured toengage a first parcel. The system further includes a second parcelcarrier selectively coupled to and removable from the UAV chassis, thesecond parcel carrier including a second engagement housing configuredto be at least partially inserted within the internal cavity of thelower portion of the UAV chassis. The second parcel carrier includes asecond power source positioned within the second engagement housing andconfigured to be electrically coupled to the plurality of propulsionmembers. A second parcel carrying mechanism of the second parcel carrieris coupled to and positioned below the second engagement housing, wherethe second parcel carrying mechanism is configured to engage a secondparcel.

In another embodiment, a UAV for delivering a parcel includes a UAVchassis including an upper portion having an upper portion widthevaluated in a lateral direction, where the upper portion includes atapered shape such that the upper portion width decreases movingdownward along the upper portion in the vertical direction. The UAVchassis includes a plurality of propulsion members configured to providelift to the UAV chassis and a lower portion positioned below the upperportion in a vertical direction. The lower portion of the UAV chassisincludes a lower portion width evaluated in the lateral direction, andthe UAV chassis includes a reduced width portion positioned between theupper portion and the lower portion, the reduced width portion having awidth evaluated in the lateral direction, where the width of the reducedwidth portion is less than the upper portion width and the lower portionwidth. The UAV further includes a parcel carrying mechanism coupled tothe lower portion, where the parcel carrying mechanism is configured toengage a parcel.

In yet another embodiment, a UAV for delivering a parcel includes a UAVchassis including an upper portion having an upper portion widthevaluated in a lateral direction and a plurality of propulsion membersconfigured to provide lift to the UAV chassis. The UAV chassis furtherincludes a reduced width portion positioned below the upper portion, thereduced width portion having a width evaluated in the lateral direction,where the width of the reduced width portion is less than the upperportion width. A parcel carrier of the UAV is selectively coupled to theUAV chassis, the parcel carrier including an engagement housingselectively coupled to the reduced width portion of the UAV chassis. Aparcel carrying mechanism of the parcel carrier is coupled to theengagement housing, where the parcel carrying mechanism is configured toengage a parcel.

In yet another embodiment, an enhanced parcel delivery system fordelivering parcels via a UAV includes a UAV support mechanism having apair of opposing rails extending in a longitudinal direction, where theopposing rails are spaced apart from one another in a lateral directionthat is transverse to the longitudinal direction. The opposing railsdefine a landing region, a takeoff region positioned opposite thelanding region, a transport region positioned between the takeoff regionand the landing region. The system further includes at least one UAVincluding a UAV chassis having an upper portion having an upper portionwidth evaluated in a lateral direction. A lower portion of the UAVchassis is positioned below the upper portion in a vertical direction,the lower portion having a lower portion width evaluated in the lateraldirection. A reduced width portion of the UAV chassis is positionedbetween the upper portion and the lower portion, the reduced widthportion having a width evaluated in the lateral direction. The width ofthe reduced width portion is less than the upper portion width and thelower portion width, and where the reduced width portion is configuredto engage the pair of opposing rails of the UAV support mechanism.

In one embodiment, a primary delivery vehicle configured for deliveringparcels via a UAV includes an interior compartment, and a roof paneldefining a portal, where the interior compartment is accessible throughthe portal. The vehicle includes a UAV support mechanism positioned onthe roof panel of the vehicle and configured for providing a landingsurface for the UAV, the UAV support mechanism including a pair ofopposing rails extending in a longitudinal direction and positionedabove the portal, where the opposing rails are spaced apart from oneanother in a lateral direction that is transverse to the longitudinaldirection. The opposing rails define a landing region, a takeoff regionpositioned opposite the landing region, and a transport regionpositioned between the takeoff region and the landing region.

In another embodiment, a primary delivery vehicle configured fordelivering parcels via a UAV includes an interior compartment, a roofpanel defining a supply portal and a return portal spaced apart from thesupply portal, where the interior compartment is accessible through thesupply portal and the return portal. The vehicle further includes a UAVsupport mechanism including a pair of opposing rails extending in alongitudinal direction, where the opposing rails are spaced apart fromone another in a lateral direction that is transverse to thelongitudinal direction. The opposing rails define a landing region, asupply region positioned over the supply portal of the roof panel, areturn region positioned over the return portal of the roof panel, and atransport region positioned between the supply region and the returnregion.

In yet another embodiment, a primary delivery vehicle configured fordelivering parcels via a UAV includes an interior compartment, a roofpanel defining a supply portal, where the interior compartment isaccessible through the supply portal, a loading robot positioned withinthe interior compartment. The loading robot includes a robot controllerincluding at least one processor and at least one memory includingprogram code, the at least one memory and the program code configuredto, with the processor, cause the loading robot to at least engage aparcel carrier, move the parcel carrier to a supply portal, and engagethe parcel carrier with a UAV positioned above the supply portal.

In yet another embodiment, a primary delivery vehicle configured fordelivering parcels via a UAV includes an interior compartment, and aroof panel defining a return portal, where the interior compartment isaccessible through the return portal. A loading robot is positionedwithin the interior compartment, the loading robot including a robotcontroller including at least one processor and at least one memoryincluding program code, the at least one memory and the program codeconfigured to, with the processor, cause the loading robot to at leastengage a parcel carrier coupled to a UAV positioned above the returnportal, remove the parcel carrier from a UAV chassis of the UAV, movethe parcel carrier from the return portal to a rack positioned in theinterior compartment, and engage the parcel carrier with the rack of theinterior compartment.

In yet another embodiment, a method for loading/unloading a parcelcarrier to a UAV includes receiving a parcel to be delivered by a UAVand engaging a parcel carrying mechanism of a parcel carrier with theparcel, the parcel carrying mechanism being configured to engage andsecure the parcel to the parcel carrier. The method further includesmoving the parcel carrier and parcel toward a UAV chassis of the UAV,and securing an engagement housing of the parcel carrier to the UAVchassis of the UAV, where the engagement housing of the parcel carrieris coupled to and positioned above the parcel carrying mechanism of theparcel carrier.

In one embodiment, a method for loading/unloading a parcel carrier to aUAV includes engaging a parcel with a parcel carrier, the parcel carrierincluding an engagement housing and a parcel carrying mechanism coupledto and positioned below the engagement housing, where the parcel isengaged with the parcel carrying mechanism. The method further includesmoving the parcel carrier toward a UAV chassis positioned on a UAVsupport mechanism, moving an engagement member of the UAV chassis froman extended position into a retracted position, engaging the engagementhousing of the parcel carrier with a UAV chassis. The method furtherincludes moving the engagement member of the UAV chassis from theretracted position into the extended positon, securing the engagementhousing to the UAV chassis.

In yet another embodiment, a method for delivering parcels via a UAVincludes securing a first parcel to a first parcel carrier, and at aloading point, securing the first parcel carrier to a chassis of a UAVfor delivery of the first parcel. The method further includes navigatingthe UAV from the loading point to a serviceable point, and at theserviceable point, releasing the first parcel from a parcel carryingmechanism of the first parcel carrier. The method further includesnavigating the UAV from the serviceable point to the loading point, andat the loading point, removing the first parcel carrier from the UAVchassis and securing a second parcel carrier that is coupled to a secondparcel to the chassis of the UAV for delivery of the second parcel.

In another embodiment, a method for accessing a restricted access areaby a UAV includes electronically storing, by a computing entity of theUAV, an access code associated with a restricted access area, where (a)the restricted access area is at a serviceable point, (b) a usercomputing entity at the serviceable point is configured to selectivelyallow access to the restricted access area in response to receipt of theaccess code, and (c) the UAV includes the UAV computing entity. Themethod further includes, after navigation of the UAV proximate therestricted access area at the serviceable point, communicating, by thecomputing entity of the UAV, the access code to the user computingentity, where (a) a parcel is selectively coupled to a UAV chassis ofthe UAV, and (b) the user computing entity allows entry into therestricted access area responsive to receiving the access code. Afterthe user computing entity allows entry into the restricted access area,the method further includes navigating, by the computing entity of theUAV, the UAV into the restricted access area of the serviceable point.

In yet another embodiment, a UAV computing entity includes at least oneprocessor and at least one memory including program code, the at leastone memory and the program code configured to, with the processor, causethe UAV computing entity to at least electronically store an access codeassociated with a restricted access area, where (a) the restrictedaccess area is at a serviceable point, (b) a user computing entity atthe serviceable point is configured to selectively allow access to therestricted access area in response to receipt of the access code, and(c) a UAV includes the UAV computing entity. After navigation of the UAVproximate the restricted access area at the serviceable point, the UAVcomputing entity is configured to communicate the access code to theuser computing entity, where (a) a parcel is selectively coupled to aUAV chassis of the UAV, and (b) the user computing entity allows entryinto the restricted access area responsive to receiving the access code.After the user computing entity allows entry into the restricted accessarea, the UAV computing entity is configured to navigate the UAV intothe restricted access area of the serviceable point.

In one embodiment, a method for picking up a parcel via a UAV includesnavigating a UAV to a serviceable point, the UAV including a UAVchassis, a parcel carrier coupled to the UAV chassis, the parcel carrierincluding an engagement housing selectively coupled to the UAV chassis,and parcel carrying arms positioned below the engagement housing. Themethod further includes detecting a parcel at the serviceable point witha camera of the UAV, navigating the UAV to a position over the parceland reducing power to propulsion members of the UAV to descend the UAVover the parcel. The method further includes depressing a ground probeof the parcel carrier, engaging the parcel carrying arms of the parcelcarrier with the parcel, and navigating the UAV from the serviceablepoint to a UAV support mechanism.

In another embodiment, a method for picking up a parcel via a UAVincludes navigating a UAV to a serviceable point, the UAV including aUAV chassis, a parcel carrier coupled to the UAV chassis, the parcelcarrier including an engagement housing selectively coupled to the UAVchassis, and a parcel carrying mechanism positioned below the engagementhousing. The method further includes landing the UAV at the serviceablepoint and turning off propulsion members of the UAV, receiving, via aUAV computing entity, a notification that a parcel is engaged with theengagement housing of the parcel carrier, and engaging the propulsionmembers of the UAV and navigating the UAV from the serviceable point toa UAV support mechanism.

In yet another embodiment, an enhanced parcel delivery system fordelivering parcels via a UAV includes a primary delivery vehicle, a UAVsupport mechanism coupled to the primary delivery vehicle, the UAVsupport mechanism configured for supporting one or more UAVs. Aplurality of UAVs of the system each include a UAV chassis including aplurality of propulsion members configured to provide lift to the UAVchassis, and a parcel carrier including an engagement housing configuredfor being secured to the UAV chassis. Each parcel carrier includes aparcel carrying mechanism coupled to and positioned below the engagementhousing, where the parcel carrying mechanism is configured for engagingand holding a parcel for delivery.

In yet another embodiment, a method for providing a notificationregarding delivery of a parcel by a UAV including after navigating a UAVto a serviceable point, establishing, via a UAV computing entity, adirect communications link between the UAV computing entity and a usercomputing entity, where (a) a UAV includes the UAV computing entity, aUAV chassis, and a parcel carrier coupled to the UAV chassis, (b) theparcel carrier includes an engagement housing selectively coupled to theUAV chassis, (c) a parcel carrying mechanism is engaged with andsecuring a parcel to the engagement housing, and (d) the user computingentity is associated with the serviceable point. The method furtherincludes releasing the parcel from the parcel carrying mechanism of theparcel carrier, and after releasing the parcel from the parcel carryingmechanism of the parcel carrier, providing, via the UAV computingentity, a notification to the user computing entity through the directcommunications link, where the notification includes informationindicative of the release of the parcel at the serviceable point.

In one embodiment, a UAV computing entity includes at least oneprocessor and at least one memory including program code, the at leastone memory and the program code configured to, with the processor, causethe UAV computing entity to at least, after navigating a UAV to aserviceable point, establish a communication link between the UAVcomputing entity and a user computing entity, where (a) a UAV includesthe UAV computing entity, a UAV chassis, and a parcel carrier coupled tothe UAV chassis, (b) the parcel carrier includes an engagement housingselectively coupled to the UAV chassis, (c) a parcel carrying mechanismis engaged with and securing a parcel to the engagement housing, and (d)the user computing entity is associated with the serviceable point,release the parcel from the parcel carrying mechanism of the parcelcarrier. After releasing the parcel from the parcel carrying mechanismof the parcel carrier, the UAV computing entity is configured to providea notification to the user computing entity through the communicationlink, where the notification includes information indicative of therelease of the parcel at the serviceable point.

In another embodiment, a method for landing an unmanned aerial (UAV) ona UAV support mechanism includes navigating a UAV toward a UAV supportmechanism, receiving a signal from a guidance array of the UAV supportmechanism, and navigating the UAV to a landing region of a UAV supportmechanism. The method further includes guiding a reduced width portionof the UAV between opposing rails of the UAV support mechanism andengaging the UAV with the UAV support mechanism, and moving the UAV fromthe landing region toward a return region of the UAV support mechanism.

In one embodiment, a method for initiating delivery of a parcel via anunmanned aerial vehicle includes, for each of a first plurality ofparcels to be delivered by a carrier, electronically storing parcel dataincluding (a) a first logical grouping identifier corresponding to afirst logical grouping with which each of the first plurality of parcelsis associated and (b) a respective parcel identifier for each of thefirst plurality of parcels. The method further includes, for each of asecond plurality of parcels to be delivered by the carrier,electronically storing parcel data including (a) a second logicalgrouping identifier corresponding to a second logical grouping withwhich each of the second plurality of parcels is associated and (b) arespective parcel identifier for each of the second plurality ofparcels. The method further includes electronically setting a currentlogical grouping identifier to the first logical grouping identifier,responsive to receiving an indication that a first parcel from thesecond plurality of parcels is to be delivered by the carrier,determining whether the logical grouping identifier for the first parcelis the same as the current logical grouping identifier, and responsiveto determining the logical grouping identifier for the first parcel isnot the same as the current logical grouping identifier, initiatingdelivery of a second parcel from the second plurality of parcels by anunmanned aerial vehicle.

In another embodiment, a system includes at least one processor and atleast one memory including program code, the at least one memory and theprogram code configured to, with the processor, cause the system to atleast, for each of a first plurality of parcels to be delivered by acarrier, electronically store parcel data including (a) a first logicalgrouping identifier corresponding to a first logical grouping with whicheach of the first plurality of parcels is associated and (b) arespective parcel identifier for each of the first plurality of parcels.For each of a second plurality of parcels to be delivered by thecarrier, the system is further configured to electronically store parceldata including (a) a second logical grouping identifier corresponding toa second logical grouping with which each of the second plurality ofparcels is associated and (b) a respective parcel identifier for each ofthe second plurality of parcels. The system is further configured toelectronically set a current logical grouping identifier to the firstlogical grouping identifier, responsive to receiving an indication thata first parcel from the second plurality of parcels is to be deliveredby the carrier, determine whether the logical grouping identifier forthe first parcel is the same as the current logical grouping identifier.Responsive to determining the logical grouping identifier for the firstparcel is not the same as the current logical grouping identifier, thesystem is further configured to initiate delivery of a second parcelfrom the second plurality of parcels by an unmanned aerial vehicle.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 schematically depicts a vehicle and a plurality of associatedUAVs according to one embodiment shown and described herein;

FIG. 2 schematically depicts a perspective view of the UAV of FIG. 1 andassociated parcel carrier according to one embodiment shown anddescribed herein;

FIG. 3 schematically depicts a top view of the UAV of FIG. 1 accordingto one embodiment shown and described herein;

FIG. 4. schematically depicts a bottom perspective view of the UAVchassis of the UAV of FIG. 1 according to one embodiment shown anddescribed herein;

FIG. 5 schematically depicts an exploded perspective view of the UAV andparcel carrier of FIG. 2 according to one embodiment shown and describedherein;

FIG. 6 schematically depicts a bottom perspective view of the UAV andparcel carrier of FIG. 2 according to one embodiment shown and describedherein;

FIG. 7 schematically depicts a bottom view of the UAV chassis and parcelcarrier of FIG. 2 according to one embodiment shown and describedherein;

FIG. 8 schematically depicts a cross-sectional view of the UAV chassis'retaining member assembly according to one embodiment shown anddescribed herein;

FIG. 9 schematically depicts a perspective view of the parcel carrier ofFIG. 5 and a parcel according to one embodiment shown and describedherein;

FIG. 10 schematically depicts a front view of the UAV of FIG. 1 andvarious sensors according to one embodiment shown and described herein;

FIG. 11 schematically depicts a top perspective view of the UAV of FIG.1 and ground landing sensors according to one embodiment shown anddescribed herein;

FIG. 12 schematically depicts a UAV control system according to oneembodiment shown and described herein;

FIG. 13 schematically depicts a parcel carrier controller according toone embodiment shown and described herein;

FIG. 14 schematically depicts a top perspective view of the UAV of FIG.1 and ground landing sensors according to one embodiment shown anddescribed herein;

FIG. 15 schematically depicts a top perspective view of the UAV of FIG.1 and ground landing sensors according to one embodiment shown anddescribed herein;

FIG. 16 schematically depicts perspective view of a parcel according toone embodiment shown and described herein;

FIG. 17 schematically depicts a perspective view of a parcel carrier anda parcel according to one embodiment shown and described herein;

FIG. 18 schematically depicts a perspective view of a parcel carrier anda parcel according to one embodiment shown and described herein;

FIG. 19 schematically depicts a perspective view of a parcel carrier anda parcel housing according to one embodiment shown and described herein;

FIG. 20 schematically depicts a perspective view of a parcel carrier andanother parcel housing according to one embodiment shown and describedherein;

FIG. 21A schematically depicts a side view of the parcel housing of FIG.20 in a closed position according to one embodiment shown and describedherein;

FIG. 21B schematically depicts a side view of the parcel housing of FIG.20 in a closed position according to one embodiment shown and describedherein;

FIG. 22 schematically depicts a bottom perspective view of a UAVincluding landing arms according to one embodiment shown and describedherein;

FIG. 23A schematically depicts a front view of another UAV chassis andparcel carrier according to one embodiment shown and described herein;

FIG. 23B schematically depicts a front view of another UAV chassis andparcel carrier according to one embodiment shown and described herein;

FIG. 24 schematically depicts a rear perspective view of the vehicle ofFIG. 1 including a UAV support mechanism according to one embodimentshown and described herein;

FIG. 25 schematically depicts a perspective view of the UAV supportmechanism of FIG. 24 according to one embodiment shown and describedherein;

FIG. 26A schematically depicts a section view of the UAV supportmechanism of FIG. 25 along section 26A-26A according to one embodimentshown and described herein;

FIG. 26B schematically depicts an enlarged section view of the UAVsupport mechanism of FIG. 26A according to one embodiment shown anddescribed herein;

FIG. 27 schematically depicts a conveyor controller according to oneembodiment shown and described herein;

FIG. 28 schematically depicts a front view of opposing rails of the UAVsupport mechanism of FIG. 24 according to one embodiment shown anddescribed herein;

FIG. 29 schematically depicts a rear perspective view of the vehicle ofFIG. 1 including racks according to one embodiment shown and describedherein;

FIG. 30 schematically depicts a rear perspective view of the vehicle ofFIG. 1 including robots according to one embodiment shown and describedherein;

FIG. 31 schematically depicts a robot controller according to oneembodiment shown and described herein;

FIG. 32 schematically depicts a perspective view of an automated parcelcarrier/parcel connection system according to one embodiment shown anddescribed herein;

FIG. 33 schematically depicts a rear perspective view of the vehicle ofFIG. 1 and a parcel conveyor according to one embodiment shown anddescribed herein;

FIG. 34 schematically depicts the parcel conveyor of FIG. 33 and therobot of FIG. 30 according to one embodiment shown and described herein;

FIG. 35A schematically depicts a perspective view of a robot loading aparcel and parcel carrier to the rack of FIG. 29 according to oneembodiment shown and described herein;

FIG. 35B schematically depicts a perspective view of a robot loading aparcel and parcel carrier to the rack of FIG. 29 according to oneembodiment shown and described herein;

FIG. 35C schematically depicts a perspective view of a robot loading aparcel and parcel carrier to the rack of FIG. 29 according to oneembodiment shown and described herein;

FIG. 36 schematically depicts a perspective view of the UAV supportmechanism of FIG. 25 including UAVs according to one embodiment shownand described herein;

FIG. 37 schematically depicts a section view of the UAV supportmechanism of FIG. 36 along section 37-37 according to one embodimentshown and described herein;

FIG. 38A schematically depicts a parcel being loaded to a UAV chassiswith the robot of FIG. 30 according to one embodiment shown anddescribed herein;

FIG. 38B schematically depicts a parcel being loaded to a UAV chassiswith the robot of FIG. 30 according to one embodiment shown anddescribed herein;

FIG. 38C schematically depicts a parcel being loaded to a UAV chassiswith the robot of FIG. 30 according to one embodiment shown anddescribed herein;

FIG. 39 schematically depicts a rear perspective view of the vehicle ofFIG. 1 and the UAV support mechanism of FIG. 24 according to oneembodiment shown and described herein;

FIG. 40 schematically depicts a side view of the UAV and the UAV supportmechanism of FIG. 24 according to one embodiment shown and describedherein;

FIG. 41 schematically depicts a front view of the opposing rails of FIG.28 and a UAV according to one embodiment shown and described herein;

FIG. 42A schematically depicts a perspective view of the robot of FIG.30 removing a parcel carrier from a UAV chassis and moving the parcelcarrier to the rack according to one embodiment shown and describedherein;

FIG. 42B schematically depicts a perspective view of the robot of FIG.30 removing a parcel carrier from a UAV chassis and moving the parcelcarrier to the rack according to one embodiment shown and describedherein;

FIG. 43 schematically depicts a rear perspective view of another vehicleincluding racks according to one embodiment shown and described herein;

FIG. 44 schematically depicts a front perspective view of anothervehicle including the UAV support mechanism of FIG. 24 according to oneembodiment shown and described herein;

FIG. 45A schematically depicts a rear perspective view of a vehicleincluding a landing pad according to one embodiment shown and describedherein;

FIG. 45B schematically depicts a front perspective view of anothervehicle including a landing pad according to one embodiment shown anddescribed herein;

FIG. 46 schematically depicts the interconnectivity of computingentities according to one embodiment shown and described herein;

FIG. 47 schematically depicts a central computing entity according toone embodiment shown and described herein;

FIG. 48 schematically depicts a user computing entity according to oneembodiment shown and described herein;

FIG. 49 schematically depicts UAV computing entity according to oneembodiment shown and described herein;

FIG. 50 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein;

FIG. 51 schematically depicts a region including one or more serviceablepoints according to one embodiment shown and described herein;

FIG. 52 schematically depicts a region including one or more serviceablepoints according to one embodiment shown and described herein;

FIG. 53 schematically depicts a region including one or more serviceablepoints according to one embodiment shown and described herein;

FIG. 54 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein;

FIG. 55 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein;

FIG. 56 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein;

FIG. 57 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein;

FIG. 58 schematically depicts a serviceable point according to oneembodiment shown and described herein;

FIG. 59 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein;

FIG. 60 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein;

FIG. 61 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein;

FIG. 62 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein;

FIG. 63 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein;

FIG. 64 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein;

FIG. 65 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein;

FIG. 66 schematically depicts a flowchart illustrating operations andprocesses that can be used in accordance with various embodiments shownand described herein; and

FIG. 67 schematically depicts a table of data stored in the centralcomputing entity of FIG. 47 according to one embodiment shown anddescribed herein.

DETAILED DESCRIPTION

Various embodiments now will be described more fully hereinafter withreference to the accompanying drawings, in which some, but not allembodiments are shown. Indeed, these inventions described herein may beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein; rather, these embodiments areprovided so that this disclosure will satisfy applicable legalrequirements. The term “or” is used herein in both the alternative andconjunctive sense, unless otherwise indicated. The terms “illustrative”and “exemplary” are used to be examples with no indication of qualitylevel. And terms are used both in the singular and plural formsinterchangeably. Like numbers refer to like elements throughout.

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theinvention pertains having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the invention is not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

As used herein, the vertical direction (e.g., the +/−Z-direction asdepicted) refers to the upward/downward direction of various componentsdescribed herein. The longitudinal direction (e.g., the +/−X-directionas depicted) refers to the forward/rearward direction of the componentsdescribed herein and is transverse to the vertical direction. Thelateral direction (e.g., the +/−Y-direction as depicted) refers to thecross-wise direction of the components described herein and istransverse to the vertical direction and the longitudinal direction.Similarly, the terms pick-up and delivery can be used interchangeably.That is, while many embodiments are described in the delivery context,the same or similar features and functionality may apply to the pick-upcontext.

As used herein, the term “parcel” may include any tangible and/orphysical object. In one embodiment, a parcel may be or be enclosed inone or more parcels, envelopes, parcels, bags, containers, loads,crates, parcels banded together, vehicle parts, pallets, drums, thelike, and/or similar words used herein interchangeably. Such parcels mayinclude the ability to communicate (e.g., via a chip (e.g., anintegrated circuit chip), RFID, NFC, Bluetooth, Wi-Fi, and any othersuitable communication techniques, standards, or protocols) with oneanother and/or communicate with various computing entities for a varietyof purposes. In this regard, in some example embodiments, a parcel maycommunicate send “to” address information/data, received “from” addressinformation/data, unique identifier codes, and/or various otherinformation/data.

1. Overview

Various embodiments of the present invention are directed to an enhancedparcel delivery system for efficiently delivering parcels in a varietyof environments. As described in detail herein, the enhanced parceldelivery system is generally comprised of a primary parcel deliveryvehicle, such as a conventional parcel delivery truck, and a pluralityof auxiliary delivery vehicles, such as unmanned aerial vehicles (“UAVs”or “drones”). As described in relation to particular embodiments, aparcel delivery vehicle is adapted to act as a mobile hub for a fleet ofUAVs configured for delivering parcels from the delivery vehicle to adelivery point/location (e.g., a home address or business). Inparticular, the parcel delivery vehicle is configured both for storingparcels to be delivered via a UAV and for providing a takeoff (e.g.,launch) and landing platform for the UAVs to depart from and return tothe delivery vehicle. To facilitate delivery of parcels by the UAVs fromthe delivery vehicle, a number of novel systems have been developed,including—as just some examples—systems for securing parcels to the UAVsand releasing parcels from the UAVs, systems for powering the UAVs,systems for managing parcels within the delivery vehicle for delivery bya UAV, and systems for guiding, controlling, and managing UAV-baseddeliveries. Each of these novel systems, among various otherimprovements, are described in greater detail herein.

As will be appreciated from the present disclosure, the variousembodiments of the enhanced parcel delivery system offer a number ofadvantages. For example, the use of UAVs to deliver packages from amobile hub in form of a delivery vehicle offers greatly enhancedflexibility in the delivery of parcels in a variety of environments. Inparticular, UAVs can traverse various geographic areas quickly and moreefficiently than a road-going vehicles. Moreover, the enhanced parceldelivery system enables multiple deliveries by multiple UAVs to occursimultaneously.

The use of UAVs launched from a common delivery vehicle also conservesfuel, particular in embodiments where the UAVs are battery powered.Moreover, UAV-based deliveries improve the efficiency of humanresources, enabling—for example—a single driver or delivery person tomanage the delivery or more parcels in less time. UAVs-based deliveries,particularly from a mobile hub in the form of a delivery vehicle, enablegreater flexibility in package routing and fleet management.

Likewise, convenience for parcel users (e.g., consignees) is alsoenhanced. As described herein, the consignee of a UAV-delivered parcelcan set particular locations and times for delivery and receiveup-to-date and interactive information relating to the delivery process.Various embodiments of the enhanced parcel delivery system will be nowbe described in detail with reference to the figures provided herein.

2. Enhanced Parcel Delivery System

FIG. 1 shows an enhanced parcel delivery system 2 according to oneembodiment. In the embodiment of FIG. 1, the parcel delivery system 2comprises a primary parcel delivery vehicle 10 and a plurality of UAVs100 configured to deliver parcels 300 from the vehicle 10. According tovarious embodiments, the UAVs 100 are configured to be dispatched fromthe vehicle 10, deliver parcels 300 to consignee locations, and returnto the vehicle 10.

In the illustrated embodiment of FIG. 1, the primary parcel deliveryvehicle 10 is a parcel delivery truck configured to be manually drivenby a parcel delivery driver. Alternatively, in some embodiments, theparcel delivery vehicle 10 may be autonomous, as will be described ingreater detail herein. The delivery vehicle 10 defines an interiorpackage cabin for storing a plurality of parcels to be delivered by theUAVs 100. As will be recognized, although the primary parcel deliveryvehicle 10 is described as a terrestrial vehicle, the primary parceldelivery vehicle 10 may be a manned or an unmanned terrestrial vehicle,aerial vehicle, nautical vehicle, and/or the like. For example, suchvehicles may include a tractor, a truck, a car, a motorcycle, a moped, aSegway, a bicycle, a golf cart, a hand truck, a cart, a trailer, atractor and trailer combination, a van, a flatbed truck, a vehicle, adrone, an airplane, a helicopter, a barge, a boat, and/or any other formof object for moving or transporting people and/or items (e.g., one ormore packages, parcels, bags, containers, loads, crates, items bandedtogether, vehicle parts, pallets, drums, the like, and/or similar wordsused herein interchangeably). The primary parcel delivery vehicle 10 maybe a hybrid vehicle for standard, manual deliveries by a driver and UAVdeliveries, helping the driver handle deliveries along a route.Alternatively, the primary parcel delivery vehicle 10 may be a manned orunmanned delivery vehicle dedicated solely to UAV deliveries.

In embodiment, the delivery vehicle's roof panel includes UAV supportmechanisms 400 that serve as parcel loading points and which areconfigured to enable the UAVs 100 to takeoff from, and land on, thedelivery vehicle 10. As will be explained in further detail, thedelivery vehicle 10 is configured such that parcels stored in thedelivery vehicle's interior package cabin can be secured to one of theUAVs 100 in an automated fashion, such that the UAV to which aparticular parcel is secured can then take off from the roof panel ofthe vehicle 10, deliver the parcel to a delivery location, and return tothe vehicle 10 for landing on the roof panel. In this way, the deliveryvehicle 10 functions as a mobile hub for UAV-based parcel deliveries.Alternatively, in some embodiments, the UAVs 100 may take off from, andmay return to and land on a building or other structure, such as awarehouse.

Various components and features of the enhanced parcel delivery system 2will now be described in turn in greater detail.

A. Parcel Delivery UAV & Parcel Carrier

FIG. 2 shows a perspective view of a parcel delivery UAV 100 and aparcel carrier 200, which is configured to be coupled to the UAV 100 andto engage a parcel to enable UAV-based delivery of the parcel. As willbe discussed in greater detail herein, the parcel carrier 200 isconfigured for being removably secured to the UAV 100 for transporting aparcel 300 (FIG. 1) and may include a power supply configured to powerthe UAV 100 when the parcel carrier 200 is engaged with the UAV 100.

i. Parcel Delivery UAV

As shown in FIG. 2, the parcel delivery UAV 100 generally comprises aUAV chassis 110 and a plurality of propulsion members 102 extendingoutwardly from the UAV chassis. The UAV chassis 110 generally defines abody of the UAV 100, which the propulsion members 102 are configured tolift and guide during flight. The propulsion members 102 may be operablebetween an “on” configuration, in which the propulsion members 102provide lift to the UAV 100, and an “off” configuration, in which thepropulsion members are stationary and/or do not provide lift to the UAV100. According to various embodiments, the UAV chassis 110 may be formedfrom any material of suitable strength and weight (including sustainableand reusable materials), including but not limited to compositematerials, aluminum, titanium, polymers, and/or the like, and can beformed through any suitable process.

In the embodiment depicted in FIG. 2, the UAV 100 is a hexacopter andincludes six separate propulsion members 102, each extending outwardlyfrom the UAV chassis 110. However, as will be appreciated from thedescription herein, the UAV 100 may include any number of propulsionmembers suitable to provide lift and guide the UAV 100 during flight.

FIG. 3 shows a top view of the UAV 100, in which the propulsion members102 are again shown extending outwardly from the perimeter of the UAVchassis 110. In the illustrated embodiment of FIG. 3, each of theplurality of propulsion members 102 includes a propeller 103 that ispositioned within a propeller guard 108. Each propeller 103 is comprisedof a plurality of blades that are configured to rotate within thepropeller guard 108 to provide lift and facilitate flight of the UAV100. In the illustrated embodiment, the propeller guards 108circumscribe the propellers 103 as the propellers 103 rotate, which mayassist in preventing inadvertent contact between the propellers 103 andvarious objects that the UAV 100 may encounter during flight. While theembodiment depicted in FIG. 3 depicts the propellers 103 as includingthree blades that are configured to rotate within the propeller guards108, it should be understood that the propellers 103 may include anysuitable number of blades configured to rotate within the propellerguards 108 and provide sufficient lift to the UAV 100.

In the illustrated embodiment, the propulsion members 102 areelectrically powered (e.g., by an electric motor that controls the speedat which the propellers 103 rotate). However, as will be recognized, thepropulsion members 102 may be powered by internal combustion enginesdriving an alternator, hydrogen fuel-cells, and/or the like. Each of thepropulsion members 102 is pivotally coupled to the UAV chassis 110 at amotorized joint 104, such that each of the propulsion members 102 mayrotate with respect to the UAV chassis 110. In particular, as shown inFIG. 3, each of the motorized joints 104 defines a joint axis 105 aboutwhich its respective propulsion member 102 rotates relative to the UAVchassis 110. By rotating with respect to the UAV chassis 110 about theaxis 105, the propulsion members 102 may direct their respective liftforces to maneuver the UAV 100 during flight. Moreover, as described ingreater detail herein, the ability of the propulsion members 102 topivot relative to the UAV chassis 110 enables the propulsion members tomaintain the UAV chassis 110 in a constant or near constant orientationrelative to the parcel carrier 200 and parcel 300 to prevent undesirablemovement of goods positioned within the parcel 300.

FIG. 4 shows a bottom perspective view of the UAV 100. As shown in FIG.4, the UAV chassis 110 generally defines an upper portion 114, a lowerportion 118 (positioned below the upper portion 114), and a reducedwidth portion 115 (positioned vertically between the upper portion 114and the lower portion 118). In the illustrated embodiment, thepropulsion members 102 are coupled to and extend around a perimeter ofthe upper portion 114 of the UAV chassis 110. Additionally, as describedin greater detail herein, the UAV chassis' upper portion 114 houses theUAV's control system 150.

The lower portion 118 of the UAV chassis 110 is configured to receiveand engage the parcel carrier 200 (FIG. 2). As such, the lower portion118 may alternatively be referred to herein as the “carrier receivingportion” of the UAV 100. In the illustrated embodiment, the lowerportion 118 extends downwardly from the UAV chassis' upper portion 114and resembles a hollow, oblique pyramid-shaped member. The lower portion118 defines an internal cavity 119 that extends upward into the lowerportion 118. The internal cavity 119 defines a bottom opening 117through which the internal cavity 119 may be accessed. As will bedescribed in greater detail herein, at least a portion of the parcelcarrier 200 (FIG. 2) may be inserted through the opening 117 and intothe internal cavity 119 in order to selectively couple the parcelcarrier 200 to the UAV chassis 110.

As shown in FIG. 4, the UAV 100 also includes at least one UAVelectrical interface 130 positioned within the lower portion's internalcavity 119. The electrical interface 130 comprises an electricalterminal, electrical contact, and/or the like, that is electricallycoupled to the propulsion members 102. In the illustrated embodiment,the UAV electrical interface 130 provides an electrical connection to apower source (e.g., located in the parcel carrier 200) to provideelectrical power to the propulsion members 102, as will be described ingreater detail herein.

FIG. 5 shows a side-view of the UAV 100 and a perspective view of theparcel carrier 200. In the illustrated embodiment, the UAV chassis'upper portion 114, lower portion 118, and reduced width portion 115define a generally hourglass shape. In particular, the upper portion 114and the lower portion 118 have a greater width (evaluated in the lateraland/or the longitudinal direction) as compared to the reduced widthportion 115. In the embodiment depicted in FIG. 5, the width of theupper portion 114 is tapered in the downward direction, such that thewidth of the upper portion 114 gradually reduces as it meets the reducedwidth portion 115. Similarly, the width of the lower portion 118 istapered in the upward direction, such that the width of the lowerportion 118 gradually increases away from the reduced width portion 115.As will be described in greater detail herein, the hourglass-profile ofthe UAV chassis 110 enables it to engage the UAV support mechanism 400provided on the roof panel of the parcel delivery vehicle 10, therebyenabling takeoff from and landing on the vehicle's roof. The UAV supportmechanism 400 may secure the UAV chassis 110 to the vehicles roof suchthat the UAV chassis 110 may remain secured to the vehicle 10 as thevehicle 10 moves.

As shown in FIGS. 4 and 5, the UAV 100 further includes landing gear116. In the illustrated embodiment, the landing gear 116 are provided onan underside or downward-facing side of the upper portion 114 of the UAVchassis. In the illustrated embodiment, the landing gear 116 comprise apair of rollers oriented to face downward in the vertical direction. Insome embodiments, the rollers of the landing gear 116 may be poweredsuch that the landing gear 116 may propel the UAV chassis along the UAVsupport mechanism 400. As will be described in greater detail herein,the landing gear 116 are configured to engage opposing rails of the UAVsupport mechanism 400 positioned on the vehicle 10 (FIG. 1) as the UAV100 takes off and lands to the vehicle 10.

In various other embodiments, the landing gear 116 may also bepositioned on opposite sides of the reduced width portion 115 of the UAVchassis in the lateral direction such that the landing gear 116 straddlethe reduced width portion 115. Furthermore, in various otherembodiments, the landing gear 116 may comprise other devices configuredfor engaging the opposing rails of the UAV support mechanism 400, suchas bearings, casters, and/or the like, that rotate with respect to theUAV chassis 110, which may assist in moving the UAV chassis 110 withrespect to opposing rails of the vehicle 10 (FIG. 1). Alternatively, insome embodiments, the landing gear 116 may include skids or pads coupledto the UAV chassis 110 which are configured to engage and slide alongthe pair of opposing rails of the vehicle 10 (FIG. 1), as will bedescribed in greater detail herein. In embodiments, the landing gear 116may be formed from a resilient material that may elastically deform whenthe UAV 100 is engaged with the opposing rails of the vehicle 10 (FIG.1).

ii. Parcel Carrier

As shown in FIG. 5, the parcel carrier 200 comprises an engagementhousing 210 and a parcel carrying mechanism 229 including a pair ofparcel carrying arms 230 extending outwardly from the engagement housing210. According to various embodiments, the parcel carrier's engagementhousing 210 defines a shape that is generally complimentary andcorresponds to the interior cavity 119 of the lower portion 118 of theUAV chassis 110. In the illustrated embodiment of FIG. 5, the engagementhousing 210 defines a generally oblique pyramid-shape that iscomplementary to the UAV chassis' inner cavity 119. As a result, theengagement housing 210 may be inserted into the cavity 119 of the lowerportion 118 of the UAV chassis 110 in order to selectively secure theparcel carrier 200 to the UAV 100 (as discussed further in relation toFIG. 7 herein). As shown in FIG. 5, the engagement housing 210 defines agreater width (evaluated in the lateral direction) at its bottom portionas compared to its width at its top portion.

In the illustrated embodiment, the parcel carrier's engagement housing210 includes a power supply 214 configured to power the UAV 100 andparcel carrier 200. In particular, the power supply 214 is configured topower the UAV 100 and parcel carrier 200 when the engagement housing 210is engaged within the inner cavity 119 of the UAV chassis' lower portion118. In the illustrated embodiment, the power supply 214 comprises abattery. However, as will be appreciated from the description herein,the power supply 214 may comprise any suitable device for providingelectrical power to the UAV 100 and parcel carrier 200 (e.g., a hydrogenfuel cell, and/or the like).

As shown in FIG. 5, the parcel carrier 200 includes at least one carrierelectrical interface 220 positioned on an upper surface of itsengagement housing 210. The carrier electrical interface 220 includes anelectrical terminal, electrical contact, and/or the like that iselectrically coupled to the power supply 214. In particular, the atleast one carrier electrical interface 220 is configured to interfacewith UAV electrical interface 130 (FIG. 4) when the parcel carrier 200is secured to the UAV 100, thereby electrically coupling the powersupply 214 to the UAV chassis 110 and providing power to the propulsionmembers 102.

As explained in greater detail herein, the propulsion members 102provide lift to the UAV 100, expending electrical energy and depletingthe charge and/or power of the power supply 214. As the engagementhousing 210, and accordingly the power supply 214, is removable from theUAV chassis 110, engagement housings 210 with depleted power supplies214 may be replaced with engagement housings 210 having charged powersupplies 214. By periodically replacing the power supply 214, the UAV100 may be provided with continuously sufficient power to performrepeated deliveries. According to certain embodiments, as the powersupply 214 is included within the engagement housing 210—which isconfigured to be selectively coupled to a parcel 300 (FIG. 9)—the powersupply 214 may be replaced to the UAV 100 each time a parcel 300 isdelivered, as will be described in greater detail herein.

As shown in FIG. 5, the parcel carrier's pair of parcel carrying arms230 extend outwardly from lateral sides of the engagement housing 210.In particular, in the illustrated embodiment of FIG. 5, the parcelcarrying arms 230 extend outwardly from a lower portion of theengagement housing 210. As discussed in greater detail herein, thisleaves the engagement housing 210 substantially unencumbered in order topermit engagement with the lower portion 118 of the UAV housing 110.

In the illustrated embodiment, the parcel carrier 200 is substantiallysymmetrical and the parcel carrying arms 230 on the opposite sidesengagement housing 210 are substantially the same. As shown in FIG. 5,the parcel carrying arms 230 each include an upper portion 232 extendinglaterally outward from the engagement housing 210, a lower portion 234that extends downward from the upper portion 232, and parcel rails 235that are positioned on the bottom portion of the lower portion 234 andthat are oriented transverse to the lower portion 234. A plurality ofpins 236 extend inward from the parcel rails 235 toward the parcel 300in the lateral direction, and are selectively positioned to engagecorresponding apertures 312 defined by the parcel 300 (FIG. 9). Theparcel carrying arms 230 and the plurality of pins 236 may be formed ofany suitable material to support the parcel 300, such as metal,composites, and/or the like, and may be formed by any suitablemanufacturing process, such as casting, forging, and/or the like.

Each of the parcel carrying arms 230 are slidably coupled to theengagement housing 210 such that the parcel carrying arms 230 aremovable in the lateral direction with respect to the engagement housing210. In particular, the parcel carrying arms 230 are repositionablebetween an inward, engaged position (e.g., in which the parcel carryingarms 230 are engaged with a parcel 300) and an outward, disengagedposition (e.g., in which the parcel carrying arms are moved furtheroutward and disengaged from a parcel 300). Alternatively, in variousother embodiments, the parcel carrying arms 230 are pivotally coupled tothe engagement housing 210 such that the parcel carrying arms 230 aremovable in the lateral direction with respect to the engagement housing210, such as by pivoting about an axis that is parallel with thelongitudinal direction as depicted.

In embodiments, the parcel carrying arms 230 may be inwardly biased inthe lateral direction, such that the parcel carrying arms 230 are biasedtoward the parcel 300 (FIG. 9) in the lateral direction. The parcelcarrying arms 230 may be inwardly biased by a biasing member, such as atension spring, a torsion spring, a compression spring, and/or the like.In this way, the parcel carrying arms 230 may be biased into the engagedposition, in which the plurality of pins 236 are positioned within theapertures 312 (FIG. 9) of the parcel 300. To move the parcel carryingarms 230 from the engaged position to the disengaged position, theparcel carrying arms 230 are coupled to a motor 213 that is configuredto overcome the inward bias of the parcel carrying arms 230, moving theparcel carrying arms 230 outward in the lateral direction into thedisengaged position. The motor 213 may be communicatively coupled to aparcel carrier controller 212 that controls operation of the motor 213,and may command the motor 213 to move the parcel carrying arms 230 fromthe engaged position into the disengaged position. By biasing the parcelcarrying arms 230 in an inward lateral direction, the parcel carryingarms 230 may engage parcels 300 having different widths evaluated in thelateral direction.

The parcel carrier 200 further includes a ground probe 250 that extendsdownward from the engagement housing 210. In the embodiment depicted inFIG. 5, the ground probe 250 is coupled to the engagement housing 210through the parcel carrying arms 230. Alternatively, the ground probe250 may be directly coupled to the engagement housing 210, or may bedirectly coupled to the parcel 300.

iii. Engagement of the UAV & Parcel Carrier

FIG. 6 shows a perspective view of the view the parcel carrier 200coupled to the UAV 100. As shown in FIG. 6, when the parcel carrier 200is installed to the UAV chassis 110, the engagement housing 210 isretained within the inner cavity 119 (FIG. 4) of the lower portion 118of the UAV chassis 110. In the illustrated embodiment, the engagementhousing 210 is retained within the inner cavity 119 by retaining members120. In particular, FIG. 7 shows an underside view of the UAV's lowerportion 118 and inner cavity 119 with the engagement housing 210inserted therein. As shown in FIG. 7, the retaining members 120 extendinward into the inner cavity 119 of the UAV chassis 110 in the lateraland/or the longitudinal directions, thereby extending beneath the lowersurface of the engagement housing 210 and retaining the engagementhousing 210 within the inner cavity 119 through mechanical interference.As described above, the engagement housing 210 and the inner cavity 119of the UAV chassis 110 include complementary shapes. When the engagementhousing 210 is installed to the inner cavity 119, the engagement housing210 may fit partially or entirely within the inner cavity 119, and oncepositioned within the inner cavity 119, may be retained within the innercavity by the one or more retaining members 120.

The retaining members 120 are movable with respect to the inner cavity119 of the UAV chassis 110 such that each of the retaining members 120move inward into and outward from the inner cavity 119. FIG. 8 providesa cross-sectional side view of one of the UAV chassis' retaining members120 according to one embodiment. As shown in FIG. 8, the retainingmember 120 is provided as part of a retaining member assembly comprisingthe retaining member 120, a biasing spring 125, and a solenoid actuator127. In the illustrated embodiment, the retaining member 120 defines asloped sidewall 121 and an upper wall 122. The retaining member 120 ismounted substantially within a wall of the UAV chassis' lower portion118 and is configured for lateral movement relative to the wall. Inparticular, the retaining member's ability to move laterally enables toextend inwardly into the lower portion's inner cavity 119 (in anextended orientation) or be recessed into the lower portion wall (in aretracted orientation).

In the illustrated embodiment of FIG. 8, the retaining member 120 isbiased to its extended orientation by a spring 125. In this orientation,the retaining member's sloped sidewall 121 and top wall 122 each extendinto the inner cavity 119. When the parcel carrier's engagement housing210 is inserted into the UAV's inner cavity 119, the engagement housing210 will contact the retaining member's sloped sidewall 121 and push theretaining member 120 laterally into its retracted orientation. Once thebottom edge of the engagement housing 210 is inserted past the plane ofthe retaining member's top wall 122, the spring 125 will push theretaining member 120 back into its extended orientation. In thisconfiguration, the retaining member 120 will extend back into the innercavity 119 such that the engagement housing's bottom edge rests on theretaining member's top wall 122, thereby securing the engagement housing210 within the UAV chassis' inner cavity 119.

When the engagement housing 210 is to be released from the UAV chassis110, the UAV control system 150 actuates the solenoid 127, which isconfigured to push the retaining member 120 in a lateral direction backinto its retracted orientation (overcoming the force of the biasingspring 125). This movement retracts the retaining member's top wall 122into the wall of the UAV chassis' lower portion 118, leaving theengagement housing 210 an unobstructed path to be disengaged from thelower portion's inner cavity 119. According to various embodiments, aplurality of retaining member assemblies of the type shown and describedin relation to FIG. 8 may be provided around the inner perimeter of theUAV chassis' lower portion 118. Moreover, as will be appreciated fromthe description herein, any suitable method of actuating the retainingmembers 120 between an extended and retracted orientation may beimplemented to enable retention of the engagement housing 210 within theUAV chassis' lower portion 118.

iv. Engagement of the Parcel Carrier with a Parcel

FIG. 9 shows a parcel 300 secured to the parcel carrier 200. Asdescribed above, the parcel carrier 200 includes parcel carrying arms230 that extend outward from the engagement housing 210. In FIG. 9, theparcel carrying arms 230 are shown in their inward, engaged position andare securing the parcel 300 to the parcel carrier 200. While one of theparcel carrying arms 230 is obscured by the parcel 300 in the embodimentdepicted in FIG. 9, it should be understood that the parcel carrier 200is substantially symmetrical and the parcel carrying arms 230 on theopposite sides of the parcel 300 are substantially the same.

In the embodiment depicted in FIG. 9, the parcel carrying arms'plurality of pins 236 extend inward from the parcel rails 235 toward theparcel 300 in the lateral direction, and are selectively positioned toengage corresponding apertures 312 defined on the parcel 300. In theillustrated embodiment, the apertures 312 are pre-formed into the sidesof the parcel 300 at locations that correspond to the placement of thepins 236 on the rails 235. However, in alternative embodiments, theplurality of pins 236 may be configured to puncture the side of theparcel 300 during engagement of the parcel 300 in order to formapertures to grip and secure the parcel 300 via the plurality of pins236. In some embodiments, the apertures 312 are pre-formed into thesides of the parcel 300, and in some embodiments, the apertures 312 maybe reinforced to support the weight of the parcel 300 when engaged withthe plurality of pins 236. Alternatively, in some embodiments, theplurality of pins 236 may form the apertures within the parcel 300 whenthe plurality of pins 236 engage the parcel 300. In other words, thepins 236 may pierce the parcel 300 to form the apertures 312. In stillother embodiments, the parcel 300 may include perforations or reducedthickness regions that may be pierced by the pins 236 to form theapertures 312.

The parcel carrying arms 230 selectively engage the parcel 300 throughengagement between the plurality of pins 236 and the apertures 312, suchthat the parcel 300 may be selectively coupled to the UAV 100 (FIG. 6)when the parcel carrier 200 is coupled to the UAV chassis 110.Alternatively, in some embodiments, the parcel 300 may include aplurality of pins that may be selectively inserted into aperturesdefined on the parcel carrying arms' rails 235.

The ground probe 250 is configured to extend downward from a bottomsurface 310 of the parcel by a distance ‘d’ evaluated between the end ofthe ground probe 250 and the bottom surface 310. The ground probe 250 isconfigured to detect when the parcel 300 is placed on a landing surface,such as when the parcel 300 is delivered to a destination by the UAV 100(FIG. 5), and may be communicatively coupled to the parcel carriercontroller 212.

When the parcel 300 is positioned on a surface, such as when the parcel300 is delivered to a destination by the UAV 100 (FIG. 5), the groundprobe 250 may contact the surface prior to a bottom surface 310 of theparcel 300. As the parcel 300 is lowered toward the surface, such as theground, the ground probe 250 may contact the surface and deflect and/orelastically deform in the vertical direction. Alternatively, in someembodiments, the ground probe 250 may be a telescoping probe that iscollapsible in the vertical direction, and the ground probe 250 maycollapse in the vertical direction upon contact with the surface, suchas the ground. As the ground probe 250 makes contact with the surface,the ground probe 250 sends a signal to the parcel carrier controller212, which then commands the motor 213 to reposition the parcel carryingarms 230 from the engaged position into the disengaged position, suchthat the parcel 300 is decoupled from the parcel carrier 200. In thisway, the ground probe 250 may assist in ensuring that the parcel 300 isnot released from the parcel carrier 200 until the parcel 300 ispositioned on or proximate to a surface, such as a landing surface wherethe parcel 300 is to be delivered. By ensuring that the parcel ispositioned on or proximate to a surface, damage to the parcel 300 may beminimized, as compared to when the parcel is released from the parcelcarrier 200 from a height above a landing surface. While the groundprobe 250 is described herein as including a probe extending downwardfrom the parcel carrying arms 230, it should be understood that theground probe 250 may include any suitable sensor for detecting adistance between the bottom surface 310 of the parcel and a surface, forexample and without limitation, a proximity sensor, a LIDAR sensor, aSONAR sensor and/or the like.

v. UAV Control System

In various embodiments, the UAV 100 includes a UAV control system 150that includes a plurality of sensing devices that assist in navigatingthe UAV 100 during flight. The plurality of sensing devices areconfigured to detect objects around the UAV 100 and provide feedback toa UAV computing entity 808 to assist in guiding the UAV 100 in theexecution of various operations, such as takeoff, flight navigation, andlanding, as will be described in greater detail herein.

FIGS. 10 and 11 show the parcel carrier 200 secured to a parcel 300 andfurther secured to the UAV 100 for delivery. In the illustratedembodiment, the UAV 100 includes a plurality of sensors, includingground landing sensors 162, vehicle landing sensors 164, flight guidancesensors 166, and one or more cameras 168. The vehicle landing sensors164 are positioned on the lower portion 118 of the UAV chassis 110 andassist in landing the UAV 100 on a vehicle 10 (FIG. 1) as will bedescribed in greater detail herein. The vehicle landing sensors 164 mayinclude one or more cameras (e.g., video cameras and/or still cameras),one or more altitude sensors (e.g., Light Detection and Ranging (LIDAR)sensors, laser-based distance sensors, infrared distance sensors,ultrasonic distance sensors, optical sensors and/or the like). Beinglocated on the lower portion 118 of the UAV chassis 110, the vehiclelanding sensors 164 are positioned below the propulsion members 102 andhave a line of sight with the opposing rails of the delivery vehicle'sUAV support mechanism 400 (FIG. 1) when the UAV 100 approaches thevehicle 10 (FIG. 1) during landing, as will be described in greaterdetail herein.

The UAV's one or more cameras 168 are also positioned on the lowerportion 118 of the UAV chassis 110, on propeller guards 108, on groundprobes 250, and/or the like. The one or more cameras 168 may includevideo and/or still cameras, and may capture images and/or video of theflight of the UAV 100 during a delivery process, and may assist inverifying or confirming delivery of a parcel 300 to a destination, aswill be described in greater detail herein. Being located on the lowerportion 118 of the UAV chassis 110, the one or more cameras 168 arepositioned below the propulsion members 102 and have an unobstructedline of sight to view the flight of the UAV 100.

The UAV's flight guidance sensors 166 are also positioned on the lowerportion 118 of the UAV chassis 110. The flight guidance sensors 166 mayinclude LIDAR, LiDAR, LADAR, SONAR, magnetic-field sensors, RADARsensors, and/or the like and may be configured to “sense and avoid”objects that the UAV 100 may encounter during flight. For example theflight guidance sensors 166 may be configured to detect objectspositioned around the UAV 100 such that the UAV 100 may determine anappropriate flight path to avoid contact with the objects. Bypositioning the flight guidance sensors 166 on the lower portion 118 ofthe UAV chassis 110, the flight guidance sensors 166 are positionedbelow the propulsion members 102 and may have an unobstructed line ofsight to view the flight of the UAV 100.

Referring in particular to FIG. 11, the UAV's ground landing sensors 162are coupled to the upper portion 114 of the UAV chassis 110. In theembodiment depicted in FIG. 11, the ground landing sensors 162 arecoupled to the propulsion members 102 at their outer perimeter on theirrespective propeller guards 108. According to various embodiments, theground landing sensors 162 are generally configured to detect a distancebetween the UAV and surfaces positioned within a line of sight 163 ofthe ground landing sensors 162. For example, during flight, the groundlanding sensors 162 may detect a distance between the UAV and a landingsurface, such as the ground or the roof of the parcel delivery vehicle100. By detecting a distance between the UAV 100 and a landing surface,the ground landing sensors 162 may assist in the takeoff and landing ofthe UAV 100. According to various embodiments, the ground landingsensors 162 may include SONAR sensors, LIDAR sensors, IR-Lock sensors,infrared distance sensors, ultrasonic distance sensors, magnetic-fieldsensors, RADAR sensors, and/or the like.

In certain embodiments, the ground landing sensors 162 may be pivotallycoupled to the propeller guards 108, such that the ground landingsensors 162 may rotate with respect to the propeller guards 108. Asnoted above, the propulsion members 102 may pivot with respect to theUAV chassis 110. Thus, the ground landing sensors 162 may pivot withrespect to the propeller guards 108, such that when the propeller guards108 pivot with respect to the UAV chassis 110, the ground landingsensors 162 may maintain the line of sight 163 downward toward a landingsurface.

In the embodiment depicted in FIG. 11, the ground landing sensors 162are positioned outside of a maximum parcel envelope 302 in which theparcel 300 is positioned. In particular, the maximum parcel envelope 302defines a maximum region in which the parcel 300 is positioned when theparcel is selectively coupled to the UAV 100. When the ground landingsensors 162 are coupled to the propulsion members 102, the groundlanding sensors 162 are positioned outside of the maximum parcelenvelope 302 defined by the parcel 300, each of the ground landingsensors 162 may maintain an unobstructed line of sight 163 to thelanding surface. For example, the ground landing sensors 162 arepositioned such that they are outside of the maximum parcel envelope 302acceptable by the parcel carrier's carrying arms 230.

Referring to FIGS. 3 and 12 collectively, the UAV 100 includes a UAVcontrol system 150. The UAV control system includes a UAV computingentity 808 that is communicatively coupled to one or more sensingelements. In general, the terms computing entity, computer, entity,device, system, and/or similar words used herein interchangeably mayrefer to, for example, one or more computers, computing entities,desktop computers, tablets, phablets, notebooks, laptops, distributedsystems, servers or server networks, blades, gateways, switches,processing devices, processing entities, relays, routers, network accesspoints, base stations, the like, and/or any combination of devices orentities adapted to perform the functions, operations, and/or processesdescribed herein. Such functions, operations, and/or processes mayinclude, for example, transmitting, receiving, operating on, processing,displaying, storing, determining, creating/generating, monitoring,evaluating, comparing, and/or similar terms used herein interchangeably.In one embodiment, these functions, operations, and/or processes can beperformed on information/data, content, information, and/or similarterms used herein interchangeably.

As shown in FIG. 13, in one embodiment, the UAV computing entity 808 mayinclude or be in communication with one or more processingelements/components 902 (also referred to as processors, processingcircuitry, processing device, and/or similar terms used hereininterchangeably) that communicate with other elements/components withinthe UAV computing entity 808 via a bus, for example. As will beunderstood, the processing elements/components 902 may be embodied in anumber of different ways. For example, the processing element/component902 may be embodied as one or more complex programmable logic devices(CPLDs), “cloud” processors, microprocessors, multi-core processors,coprocessing entities, application-specific instruction-set processors(ASIPs), microcontrollers, and/or controllers. Further, the processingelement/component 902 may be embodied as one or more other processingdevices or circuitry. The term circuitry may refer to an entirelyhardware embodiment or a combination of hardware and computer programproducts. Thus, the processing element/component 902 may be embodied asintegrated circuits, application specific integrated circuits (ASICs),field programmable gate arrays (FPGAs), programmable logic arrays(PLAs), hardware accelerators, other circuitry, and/or the like. As willtherefore be understood, the processing element/component 902 may beconfigured for a particular use or configured to execute instructionsstored in volatile or non-volatile media or otherwise accessible to theprocessing element/component 902. As such, whether configured byhardware or computer program products, or by a combination thereof, theprocessing element/component 902 may be capable of performing steps oroperations according to embodiments of the present invention whenconfigured accordingly.

In one embodiment, the UAV computing entity 808 may further include orbe in communication with memory components/elements—such as non-volatilemedia (also referred to as non-volatile storage, memory, memory storage,memory circuitry and/or similar terms used herein interchangeably). Inone embodiment, the non-volatile storage or memory may include one ormore non-volatile storage or memory media 904, including but not limitedto hard disks, ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memorycards, Memory Sticks, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJGRAM, Millipede memory, racetrack memory, and/or the like. As will berecognized, the non-volatile storage or memory media may storedatabases, database instances, database management systems,information/data, applications, programs, program modules, scripts,source code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, and/or the like. The termdatabase, database instance, database management system, and/or similarterms used herein interchangeably may refer to a collection of recordsor data that is stored in a computer-readable storage medium using oneor more database models, such as a hierarchical database model, networkmodel, relational model, entity-relationship model, object model,document model, semantic model, graph model, and/or the like.

In one embodiment, the memory components/elements may further include orbe in communication with volatile media (also referred to as volatilestorage, memory, memory storage, memory circuitry and/or similar termsused herein interchangeably). In one embodiment, the volatile storage ormemory may also include one or more volatile storage or memory media906, including but not limited to random access memory (RAM), dynamicrandom access memory (DRAM), static random access memory (SRAM), fastpage mode dynamic random access memory (FPM DRAM), extended data-outdynamic random access memory (EDO DRAM), synchronous dynamic randomaccess memory (SDRAM), double data rate synchronous dynamic randomaccess memory (DDR SDRAM), double data rate type two synchronous dynamicrandom access memory (DDR2 SDRAM), double data rate type threesynchronous dynamic random access memory (DDR3 SDRAM), Rambus dynamicrandom access memory (RDRAM), Twin Transistor RAM (TTRAM), Thyristor RAM(T-RAM), Zero-capacitor (Z-RAM), Rambus in-line memory module (RIMM),dual in-line memory module (DIMM), single in-line memory module (SIMM),video random access memory (VRAM), cache memory (including variouslevels), flash memory, register memory, and/or the like. As will berecognized, the volatile storage or memory media may be used to store atleast portions of the databases, database instances, database managementsystems, information/data, applications, programs, program modules,scripts, source code, object code, byte code, compiled code, interpretedcode, machine code, executable instructions, and/or the like beingexecuted by, for example, the processing element/component 902. Thus,the databases, database instances, database management systems,information/data, applications, programs, program modules, scripts,source code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, and/or the like may be used tocontrol certain aspects of the operation of the UAV computing entity 808with the assistance of the processing element/component 902 andoperating system.

As indicated, in one embodiment, the central computing entity 802 mayalso include one or more communications components/elements 908 forcommunicating with various computing entities, such as by communicatinginformation/data, content, information, and/or similar terms used hereininterchangeably that can be transmitted, received, operated on,processed, displayed, stored, and/or the like. Such communication may beexecuted using a wired data transmission protocol, such as fiberdistributed data interface (FDDI), digital subscriber line (DSL),Ethernet, asynchronous transfer mode (ATM), frame relay, data over cableservice interface specification (DOCSIS), or any other wiredtransmission protocol. Similarly, the central computing entity 802 maybe configured to communicate via wireless external communicationnetworks using any of a variety of protocols, such as general packetradio service (GPRS), Universal Mobile Telecommunications System (UMTS),Code Division Multiple Access 2000 (CDMA2000), CDMA2000 1× (1×RTT),Wideband Code Division Multiple Access (WCDMA), Global System for MobileCommunications (GSM), Enhanced Data rates for GSM Evolution (EDGE), TimeDivision-Synchronous Code Division Multiple Access (TD-SCDMA), Long TermEvolution (LTE), Evolved Universal Terrestrial Radio Access Network(E-UTRAN), Evolution-Data Optimized (EVDO), High Speed Packet Access(HSPA), High-Speed Downlink Packet Access (HSDPA), IEEE 802.11 (Wi-Fi),Wi-Fi Direct, 802.16 (WiMAX), ultra wideband (UWB), infrared (IR)protocols, near field communication (NFC) protocols, Wibree, Bluetoothprotocols, wireless universal serial bus (USB) protocols, and/or anyother wireless protocol.

In embodiments, each of the ground landing sensors 162, the vehiclelanding sensors 164, the flight guidance sensors 166, and the one ormore cameras 168 are communicatively coupled to a UAV computing entity808, and in particular the processing component 902 of the UAV computingentity 808. The UAV computing entity 808 may send signals to and receivesignals from the ground landing sensors 162, the vehicle landing sensors164, the flight guidance sensors 166, and the one or more cameras 168.The UAV computing entity 808 is also communicatively coupled to thepropulsion members 102 and may command the propulsion members 102 torotate, and/or may command the motorized joints 104 to pivot thepropulsion members 102 to rotate about the joint axis 105.

Moreover, the UAV 100 may include GPS sensors and/or other satellitesystem sensors for detecting a current location of the UAV relative toan intended travel destination (e.g., a destination location and/or avehicle). In various embodiments, the UAV control system 150 maycomprise a communications port (e.g., 3G, 4G, 5G communication ports)such that the UAV control system 150 may communicate with one or moreadditional computing entities.

Referring to FIGS. 9 and 13, collectively the parcel carrier controller212 is schematically depicted. The parcel carrier controller 212generally includes parcel carrier computing entity 807 comprising aprocessing component 902, a volatile memory 906, a non-volatile memory904, and a communications component 908, as described above with respectto the UAV computing entity 808. As described above, the parcel carriercontroller 212 is communicatively coupled to the motor 213 of the parcelcarrier 200, for example via the communications component 908, andcontrols operation of the motor 213 to move the parcel carrying arms 230between the engaged position and the disengaged position. The parcelcarrier controller 212 is also communicatively coupled to the groundprobe 250, for example via the communications component 908, and mayreceive signals from the ground probe 250 indicating that the groundprobe 250 has contacted a surface, such as a landing surface.Furthermore, the parcel carrier computing entity 807 may communicatewith the UAV computing entity 808 via the communications component 908and may exchange data/information with the UAV computing entity 808, forexample, a state of charge of the power supply 214 of the parcel carrier200.

As described above, the communications component 908 may include forcommunicating with various computing entities, such as by communicatinginformation/data, content, information, and/or similar terms used hereininterchangeably that can be transmitted, received, operated on,processed, displayed, stored, and/or the like. Such communication may beexecuted using a wired data transmission protocol, such as FDDI, DSL,ATM, frame relay, DOCSIS, or any other wired transmission protocol.Similarly, the central computing entity 802 may be configured tocommunicate via wireless external communication networks using any of avariety of protocols, such as GPRS, UMTS, CDMA2000, 1×RTT, WCDMA, GSM,EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct,WiMAX, UWB, IR protocols, NFC protocols, Wibree, Bluetooth protocols,wireless USB protocols, and/or any other wireless protocol.

vi. Further Embodiments of the UAV, Parcel Carrier, and Parcel

As can be understood, various modifications and changes to the UAV 100,the parcel carrier 200, and the parcel 300 as described above in FIGS.1-13 are contemplated. Description will now be made to variousalternative embodiments for the UAV 100, the parcel carrier 200, and theparcel 300.

In some embodiments, the UAV 100 may include an independent UAV powersource that provides power to the propulsion members 102, and the parcelcarrier 200 is used to couple the parcel 300 to the UAV chassis 110. Inother words, in some embodiments, the parcel carrier 200 may not includethe power supply 214 and/or the power supply 214 may not provide powerto the propulsion members 102, and the propulsion members 102 of the UAV100 may be powered by the UAV power source. Furthermore, when the UAV100 includes an independent UAV power source, in some embodiments, thepower supply 214 of the parcel carrier 200 may provide power to arefrigeration unit of the parcel 300 and may remain with the parcel 300upon delivery, as will be described in greater detail herein.

FIG. 14 shows an alternative configuration of the ground landing sensor162. Similar to the embodiment described above and depicted in FIG. 11,the ground landing sensor 162 is configured to detect a distance betweenthe ground landing sensor 162 and surfaces positioned within a line ofsight 163 of the ground landing sensor 162. For example, during flight,the ground landing sensors 162 may detect a distance between the groundlanding sensors 162, and accordingly the UAV 100, and a landing surface,such as the ground. By detecting a distance between the UAV 100 and alanding surface, the ground landing sensors 162 may assist in thetakeoff and landing of the UAV 100. The ground landing sensors 162 mayinclude SONAR sensors, LIDAR sensors, IR-Lock sensors, infrared distancesensors, ultrasonic distance sensors, magnetic-field sensors, RADARsensors, and/or the like.

In the embodiment depicted in FIG. 14, the ground landing sensor 162 iscoupled to a support member 164 that extends outside of the maximumparcel envelope 302 in which the parcel 300 is positioned. The groundlanding sensor 162 is coupled to the support member 164 such that theground landing sensor 162 is positioned outside of the maximum parcelenvelope 302. Similar to the embodiment described above in FIG. 11, bypositioning the ground landing sensor 162 outside of the maximum parcelenvelope 302, the ground landing sensor 162 may maintain an unobstructedline of sight 163 with the landing surface as the UAV 100 maneuvers.Further, the ground landing sensor 162 may be pivotally coupled to thesupport member 164 and/or the support member 164 may be pivotallycoupled to the UAV chassis 110 such that the ground landing sensor 162maintains the line of sight 163 with the landing surface as the UAV 100maneuvers during flight.

Referring to FIG. 15, another configuration of the ground landing sensor162 is schematically depicted. Similar to the embodiment described aboveand depicted in FIG. 14, the UAV 100 includes the support member 164extending outward from the UAV chassis 110. However, in the embodimentdepicted in FIG. 15, a reflective member 165 is coupled to the supportmember 164, and the ground landing sensor 162 is coupled to the UAVchassis 110. The ground landing sensor 162 has a line of sight 163 thatinitially extends outward from the UAV chassis 110 and is redirecteddownward by the reflective member 165. The ground landing sensor 162 isconfigured to detect a distance between the landing sensor 162 andsurfaces positioned within a line of sight 163 of the landing sensors162. For example, during flight, the ground landing sensors 162 maydetect a distance between the ground landing sensors 162, andaccordingly the UAV 100, and a landing surface, such as the ground. Bydetecting a distance between the UAV 100 and a landing surface, theground landing sensors 162 may assist in the takeoff and landing of theUAV 100. The ground landing sensors 162 may include SONAR sensors, LIDARsensors, IR-Lock sensors, infrared distance sensors, ultrasonic distancesensors, magnetic-field sensors, RADAR sensors, and/or the like.

In the embodiment depicted in FIG. 15, the reflective member 165 iscoupled to the support member 164, which extends outside of the maximumparcel envelope 302. The reflective member 165 is coupled to the supportmember 164 such that the reflective member 165 is positioned outside ofthe maximum parcel envelope 302. As the ground landing sensor 162 iscoupled to the UAV chassis 110 and the line of sight 163 is reflectedoff of the reflective member 165 positioned at the end of the supportmember 164, the distance that the support member 164 extends outwardfrom the UAV chassis 110 may be considered when estimating the positionof the UAV 100 with respect to a landing surface. By positioning thereflective member 165 outside of the maximum parcel envelope 302, thereflective member 165 may redirect the line of sight 163 of the groundlanding sensor 162 such that the line of sight 163 is directed downwardin the vertical direction and positioned outside of the maximum parcelenvelope 302. Further, the reflective member 165 may be pivotallycoupled to the support member 164 and/or the support member 164 may bepivotally coupled to the UAV chassis 110 such that the ground landingsensor 162 maintains the line of sight 163 with the landing surface.

As will be recognized, according to various embodiments, the UAV 100 andparcel carrier 200 (FIG. 5) may be utilized to carry parcels 300 ofdifferent sizes and shapes.

Referring to FIG. 16, another embodiment of the parcel 300 isschematically depicted. In the embodiment depicted in FIG. 16, theparcel 300 includes a generally cylindrical shape. The shape of theparcel 300 may be adapted to the particular specifications of the goodsbeing transported, and while the embodiment depicted in FIG. 16 includesa generally cylindrical shape, it should be understood that the parcel300 may include any one of a number of irregular shapes, including, butnot limited to, a spherical shape, a triangular prism shape, a conicalshape, and/or the like. For example, in some applications, such as whenthe goods being transported within the parcel 300 are refrigerated orcooled, the parcel 300 may be shaped to minimize heat exchange betweenthe interior of the parcel 300 and the surrounding environment.Furthermore, in some embodiments, the power supply 214 may be configuredto remain with the parcel 300 to provide power to a refrigeration unit217. In other embodiments, the refrigeration unit 217 may include aseparate power source positioned within the refrigeration unit 217 thatprovides power to the refrigeration unit 217.

In the embodiment depicted in FIG. 16, the parcel 300 is positionedwithin a rectangular frame 320. The parcel 300 depicted in FIG. 16 isconfigured to be used with the same parcel carrier 200 described aboveand depicted in FIG. 9. In the embodiment depicted in FIG. 16, theplurality of pins 236 extend inward from the parcel rails 235 toward theparcel frame 320 in the lateral direction, and are selectivelypositioned to engage corresponding apertures 322 defined by the parcelframe 320. The parcel carrying arms 230 selectively engage the parcelframe 320 through engagement between the plurality of pins 236 and theapertures 322, such that the parcel 300 may be selectively coupled tothe UAV 100 (FIG. 6) when the parcel carrier 200 is coupled to the UAVchassis 110. Alternatively, in some embodiments, the parcel frame 320may include a plurality of pins that may be selectively inserted intoapertures defined by the parcel carrying arms.

As described above with respect to FIG. 9, each of the parcel carryingarms 230 are movable in the lateral direction with respect to the parcel300 and the parcel frame 320 such that the plurality of pins 236 areselectively positioned within the apertures 322 defined by the parcelframe 320. The parcel carrying arms 230 are repositionable between anengaged position, in which the plurality of pins 236 are positionedwithin the apertures 322 of the parcel frame 320, and a disengagedposition, in which the plurality of pins 236 are spaced apart from theapertures 322 of the parcel frame 320. As described above with respectto FIG. 9, the parcel carrying arms 230 may be inwardly biased, and theparcel carrying arms 230 are moved between the disengaged position andthe engaged position by the motor 213.

The parcel carrier 200 further includes the ground probe 250 thatextends downward from the engagement housing 210. The ground probe 250is configured to extend downward from a bottom surface 324 of the parcelframe 320 by a distance ‘d’ evaluated between the end of the groundprobe 250 and the bottom surface 324. As described above with respect toFIG. 9, the ground probe 250 is configured to detect when the parcelframe 320, and accordingly, the parcel 300, is placed on a surface, suchas when the parcel 300 is delivered to a destination by the UAV 100(FIG. 5), and is communicatively coupled to the parcel carriercontroller 212.

Referring to FIG. 17, a perspective view of alternative embodiment ofthe parcel carrier 200 is schematically depicted. In the illustratedembodiment of FIG. 17, the parcel carrier 200 includes parcel carryingarms 230 that extend outward from the engagement housing 210. However,in the embodiment depicted in FIG. 17, the parcel carrier 200 includes apair of support flanges 238 that extend underneath the bottom surface310 of the parcel. While one of the parcel carrying arms 230 is obscuredby the parcel 300 in the embodiment depicted in FIG. 17, it should beunderstood that the parcel carrier 200 is substantially symmetrical andthe parcel carrying arms 230 on the opposite sides of the parcel 300 aresubstantially the same. In the embodiment depicted in FIG. 17, theparcel carrying arms 230 include an upper portion 232 extendinglaterally outward from the engagement housing 210, a lower portion 234that extends downward from the upper portion 232, and the support flange238 that extends laterally inward from the lower portion 234. Thesupport flange 238 may be coated with a material having a relativelyhigh coefficient of friction (e.g., high-grip rubber), thereby reducingthe likelihood that the parcel 300 may rotate about the lateraldirection with respect to the parcel carrier 200. Alternatively, thesupport flange 238 may extend at least partially in the longitudinaldirection to support the parcel 300, thereby reducing the likelihoodthat the parcel 300 may rotate about the lateral direction with respectto the parcel carrier 200.

In the embodiment of FIG. 17, the parcel carrier's housing 210, upperportion 232, lower portion 234, and ground probe 250 are substantiallythe same as the embodiment described above with respect to FIG. 9.Accordingly, each of the parcel carrying arms 230 are movable in thelateral direction with respect to the parcel 300 such that the supportflanges 238 are selectively positioned beneath the bottom surface 310 ofthe parcel 300. In particular, the parcel carrying arms 230 may includean inward bias and are repositionable between an engaged position, inwhich the support flanges 238 are positioned beneath the bottom surface310 of the parcel 300, and a disengaged position, in which the supportflanges 238 are spaced apart from the bottom surface 310 of the parcel310.

Referring to FIG. 18, further embodiments of the parcel carrier 200 andparcel 300 are schematically depicted being secured to one another. Asshown in FIG. 18, the parcel 300 includes a generally cylindrical shape.In the embodiment depicted in FIG. 18, the parcel carrying arms 230directly engage the parcel 300. In the illustrated embodiment, theparcel carrying arms 230 extend around the perimeter 301 of the parcelsuch that the parcel carrying arms 230 extend below a centerline 303that bisects the parcel 300 in the vertical direction to support theparcel 300. In other embodiments, such as embodiments in which theparcel carrying arms 230 do not extend below the centerline 303, theparcel carrying arms 300 may support the parcel 300, such as by frictionand/or mechanical interference between the parcel carrying arms 230 andthe perimeter 301 of the parcel 300. In the embodiment depicted in FIG.18, the pins 236 of the parcel carrying arms 230 engage with apertures312 defined by the parcel 300. Alternatively, in some embodiments, theparcel 300 may include a plurality of pins that may be selectivelyinserted into apertures defined by the parcel carrying arms.

As described above, the shape of the parcel 300 may be adapted to theparticular specifications of the goods being transported, and while theembodiment depicted in FIG. 18 includes a generally cylindrical shape,it should be understood that the parcel 300 may include any one of anumber of irregular shapes, including, but not limited to, a sphericalshape, a triangular prism shape, a conical shape, and/or the like. Insome embodiments, the

In the embodiment depicted in FIG. 18, the parcel carrying arms 230include a radius of curvature that is configured to extend at leastpartially around the perimeter 301 of the parcel 300. While one of theparcel carrying arms 230 is obscured by the parcel 300 in the embodimentdepicted in FIG. 18, it should be understood that the parcel carrier 200is substantially symmetrical and the parcel carrying arms 230 on theopposite sides of the parcel 300 are substantially the same. The parcelcarrying arms 230 may be formed from a material having a relatively highcoefficient of friction between the parcel carrying arms 230 and theparcel 300, thereby reducing the likelihood that the parcel 300 mayrotate about the lateral direction with respect to the parcel carrier200. Alternatively, the parcel carrying arms 230 may extend at leastpartially in the longitudinal direction to support the parcel 300,thereby reducing the likelihood that the parcel 300 may rotate about thelateral direction with respect to the parcel carrier 200.

Each of the parcel carrying arms 230 are movable in the lateraldirection with respect to the parcel 300 such that parcel carrying arms230 are selectively positioned around the perimeter 301 of the parcel300. Similar to the embodiment described above with respect to FIG. 9,the parcel carrying arms 230 may be slidably or pivotally coupled to theparcel housing 210. The parcel carrying arms 230 are repositionablebetween an engaged position, in which the parcel carrying arms 230 arepositioned at least partially around the perimeter 301 of the parcel300, and a disengaged position, in which the parcel carrying arms 230are spaced apart from the perimeter 301 of the parcel in the lateraland/or the longitudinal directions. Similar to the embodiment describedabove with respect to FIG. 9, the parcel carrying arms 230 may beinwardly biased, and the parcel carrying arms 230 are moved between thedisengaged position and the engaged position by the motor 213.

The parcel carrier 200 includes the ground probe 250 which is coupled tothe parcel carrying arms 230 and extends downward from the perimeter 301of the parcel 300 by a distance “d.” Similar to the embodiment describedabove with respect to FIG. 9, the ground probe 250 communicates with themotor 213 to selectively release the parcel 300 from the parcel carrier200.

Referring to FIG. 19, another embodiment of the parcel carrier 200 isschematically depicted. Similar to the embodiments described above, theparcel carrier 200 includes the engagement housing 210 and the powersource 214. However, in the embodiment depicted in FIG. 19, the parcelcarrier 200 is coupled to a parcel carrying mechanism 229 including aparcel housing 360, into which parcels may be positioned for delivery.The parcel housing 360 generally defines an enclosed housing having anopening 361 positioned on a side of the parcel housing 360. The opening361 is selectively covered by a door 362 that is pivotably connected tothe housing 360 and adjustable between an open position, in which theinterior of the parcel housing 360 is accessible through the opening361, and closed position, in which the interior of the parcel housing360 is enclosed. In various embodiments, the door 362 is moved betweenthe open position and the closed position by the parcel carrier's motor213, which is controlled by the parcel carrier controller.

The parcel housing 360 further includes bearing rails 364 positioned ona floor of the parcel housing 360, which reduce friction between theparcel 300 (FIG. 17) and the floor of the parcel housing 360, such thatthe parcel 300 may be easily moved into and out of the interior of theparcel housing 360 through the opening 361.

The parcel carrier 200 further includes the ground probe 250 thatextends downward from the engagement housing 210. In the embodimentdepicted in FIG. 19, the ground probe 250 is coupled to the engagementhousing 210 through the parcel housing 360. Alternatively, the groundprobe 250 may be directly coupled to the engagement housing 210. Theground probe 250 is configured to extend downward from the bottomsurface 365 of the parcel housing 360 by a distance ‘d’ evaluatedbetween the end of the ground probe 250 and the bottom surface 365 ofthe parcel housing 360. The ground probe 250 is configured to detectwhen the parcel housing 360 is placed on a surface, such as when theparcel housing 360 delivers a parcel and the ground probe 250 iscommunicatively coupled to the parcel carrier controller 212.

When the parcel housing 360 is positioned on a surface, such as when theparcel 300 is delivered to a destination by the UAV 100 (FIG. 5), theground probe 250 may contact the surface prior to a bottom surface 365of the parcel housing 360. As the parcel housing 360 is lowered towardthe landing surface, such as the ground, the ground probe 250 maycontact the landing surface and deflect and/or elastically deform in thevertical direction. Alternatively, in some embodiments, the ground probe250 may be a telescoping probe that is collapsible in the verticaldirection, and the ground probe 250 may collapse in the verticaldirection upon contact with the surface, such as the ground. As theground probe 250 makes contact with the surface, the ground probe 250sends a signal to the parcel carrier controller 212, which then commandsthe motor to move the door 362 to move from the closed position into theopen position. In this way, the ground probe 250 assists in ensuringthat the parcel 300 is not released from the parcel housing 360 untilthe parcel housing 360 is positioned on or proximate to a surface. Byensuring that the parcel housing 360 is positioned on or proximate to asurface, damage to the parcel 300 may be minimized, as compared to whenthe parcel is released from the parcel housing 360 from a height.

Once the door 362 is in the open position, the parcel 300 (FIG. 17) bemanually removed from the interior of the parcel housing 360 via theopening 361 by a parcel consignee. In particular, in some embodiments,when the door 362 is moved into the open position, the UAV 100 (FIG. 5)may maneuver such that the parcel housing 360 is tilted and the parcel300 moves along the bearing rails 364 and out of the parcel housing 360.

Referring collectively to FIGS. 20, 21A, and 21B, yet another embodimentof the parcel carrier 200 is schematically depicted. In the illustratedembodiment, the parcel housing 360 generally defines and enclosedhousing 360 having an opening 361 positioned on a side of the parcelhousing 360. The opening 361 is selectively covered by a door 362 andthe parcel housing 360 is repositionable between an open position, inwhich the interior of the parcel housing 360 is accessible through theopening 361, and closed position, in which the interior of the parcelhousing 360 is enclosed by the door 362. In the embodiment depicted inFIGS. 20, 21A, and 21B, the parcel housing 360 includes an upper portion370 that is pivotally coupled to a lower portion 372 at a pivot joint366.

Referring in particular to FIGS. 21A and 21B, the parcel housing 360 isdepicted in a closed position and an open position, respectively. In theclosed position, the lower portion 372 is engaged with the upper portion370 of the parcel housing 360 such that the door 362 covers the opening361 of the parcel housing 360. In the open position, the lower portion372 pivots with respect to the upper portion 370 about the pivot joint366, such that the opening 361 is spaced apart from the door 362 in thevertical direction and the interior of the parcel housing 360 may beaccessed through the opening 361. In particular, as the lower portion372 pivots with respect to the upper portion 370, the door 362 mayremain stationary with respect to the upper portion 370 such that thelower portion 362 and the opening 361 of the parcel housing 360 movedownward with respect to the door 362 in the vertical direction. As thelower portion 372 pivots, the lower portion 372 may become tilted withrespect to a landing surface, such as the ground, such that gravity mayinduce the parcel 300 to move downward and out of the parcel housing360.

The parcel housing 360 further includes bearing rails 364 positioned ona floor of the parcel housing 360, which may reduce friction between aparcel 300 and the floor of the parcel housing 360, such that the parcel300 may be easily moved into and out of the interior of the parcelhousing 360 through the opening 361.

The parcel carrier 200 further includes the ground probe 250 thatextends downward from the engagement housing 210. In the embodimentdepicted in FIGS. 20, 21A, 21B, the ground probe 250 is coupled to theengagement housing 210 through the parcel housing 360. Alternatively,the ground probe 250 may be directly coupled to the engagement housing210. The ground probe 250 is configured to extend downward from thebottom surface 365 of the parcel housing 360 by a distance ‘d’ evaluatedbetween the end of the ground probe 250 and the bottom surface 365 ofthe parcel housing 360. The ground probe 250 is configured to detectwhen the parcel housing 360 is placed on a surface, such as when theparcel housing 360 delivers a parcel and the ground probe 250 iscommunicatively coupled to the parcel carrier controller 212.

When the parcel housing 360 is positioned on a surface, such as when theparcel 300 is delivered to a destination by the UAV 100 (FIG. 5), theground probe 250 may contact the surface prior to a bottom surface 365of the parcel housing 360. As the parcel housing 360 is lowered towardthe surface, such as the ground, the ground probe 250 may contact thesurface and deflect and/or elastically deform in the vertical direction.Alternatively, in some embodiments, the ground probe 250 may be atelescoping probe that is collapsible in the vertical direction, and theground probe 250 may collapse in the vertical direction upon contactwith the surface, such as the ground. As the ground probe 250 makescontact with the surface, the ground probe 250 sends a signal to theparcel carrier controller 212. Upon receiving a signal from the groundprobe 250, the parcel carrier controller 213 may command the motor 213to move the lower portion 372 from the closed position in to the openposition, such that the parcel 300 will slide out of the parcelcarrier's housing 360 through the opening 361. In some embodiments, themotor 213 may rotate the lower portion 372 from the closed position tothe open position. Alternatively, in some embodiments, movement of thelower portion 372 with respect to the upper portion 370 about the pivotjoint 366 may be unpowered, and may be induced by gravitational forces.In this way, the ground probe 250 may assist in ensuring that the parcel300 is not released from the parcel housing 360 until the parcel housing360 is positioned on or proximate to a surface. By ensuring that theparcel housing 360 is positioned on or proximate to a surface, damage tothe parcel 300 may be minimized, as compared to when the parcel isreleased from the parcel housing 360 from a height.

Referring to FIG. 22 a perspective view of another embodiment of the UAVchassis 110 is schematically depicted. In the embodiment depicted inFIG. 22, landing arms 140 are coupled to and extend downward from theUAV chassis 110 in the vertical direction. The landing arms 140 areconfigured to extend outward from the maximum parcel envelope 312 of theparcel 300 in the lateral and the longitudinal directions, and thelanding arms 140 are configured to extend downward below the parcel 300.The landing arms 140 may support the UAV chassis 110 when the UAV 100 ispositioned on a surface, such as during landing and takeoff. The landingarms 140 may be relatively flexible, such that the landing arms 140 mayelastically deform when supporting the weight of the UAV chassis 110,which may assist in slowing vertical movement of the UAV chassis 110during landing. Alternatively, in some embodiments, the landing arms 140may be relatively rigid such that the landing arms 140 do not deformwhen supporting the weight of the UAV chassis 110. In the embodimentshow in FIG. 3, three landing arms 140 are coupled to the UAV chassis110, however, it should be understood that the UAV 100 may include anysuitable number of landing arms 140 to support the UAV chassis 110 on asurface.

Referring to FIG. 23A, a perspective view of another UAV chassis 110 anda parcel carrier 200 is schematically depicted. In the embodimentdepicted in FIG. 23A, the UAV chassis 110 includes the upper portion 114and the reduced width portion 115, and the parcel carrier 200 includesthe parcel carrier housing 210. However, in the embodiment depicted inFIG. 23A, the UAV chassis 110 does not include the lower portion, andthe parcel carrier housing 210 is directly coupled to the reduced widthportion 115 of the UAV chassis 110. Accordingly, the parcel carrierhousing 210 of the parcel carrier 200, and the reduced width portion 115and the upper portion 114 of the UAV chassis 110 form the tapered orhourglass shape that is configured to engage a pair of opposing rails onthe vehicle 10 (FIG. 1) as the UAV 100 takes off and lands to thevehicle 10. In particular, the upper portion 114 and the parcel carrierhousing 210 may have a greater width evaluated in the lateral and/or thelongitudinal direction as compared to the reduced width portion 115. Inthe embodiment depicted in FIG. 23A, the width of the upper portion 114evaluated in the lateral direction decreases moving downward along theupper portion 114 toward the reduced width portion 115. The width of theparcel carrier housing 210, evaluated in the lateral direction,decreases moving downward along the parcel carrier housing 210, givingthe UAV 100 a tapered or hourglass shape when the parcel carrier housing210 is coupled to the UAV chassis 110.

In the embodiment depicted in FIG. 23A, the UAV electrical interface 130is positioned on the reduced width portion 115 and is positioned toalign with the carrier electrical interface 220 when the parcel carrier200 is coupled to the UAV chassis 110. The UAV chassis 110 may includethe retaining members 120 (FIG. 7) that may selectively engage theparcel carrier housing 210 to couple the parcel carrier 200 to the UAVchassis 110. Alternatively, in some embodiments, the parcel carrierhousing 210 may be coupled to the UAV chassis 110 in any suitablemanner, such as an electromagnet and/or the like.

Referring to FIG. 23B, a perspective view of another UAV chassis 110 andparcel carrier 200 is schematically depicted. In the embodiment depictedin FIG. 23B, the UAV chassis 110 includes the upper portion 114, and theparcel carrier 200 includes a receiving portion 270 positioned above theparcel carrier housing 210. The receiving portion 270 includes an upperportion 271 and reduced width portion 274 positioned below the upperportion 271. The upper portion 271, the reduced width portion 274, andthe parcel carrier housing 210 form the tapered or hourglass shape thatis configured to engage a pair of opposing rails on the vehicle 10(FIG. 1) as the UAV 100 takes off and lands to the vehicle 10. In theembodiment depicted in FIG. 23B, the width of the upper portion 271evaluated in the lateral direction decreases moving downward along theupper portion 271 toward the reduced width portion 274. The width of theparcel carrier housing 210, evaluated in the lateral direction,increases moving downward along the parcel carrier housing 210 from thereduced width portion 274, giving the parcel carrier housing 210 andreceiving portion 270 an hourglass or tapered shape.

The receiving portion 270 includes an upper portion 271 that defines acavity 272 which is configured to receive the upper portion 114 of theUAV chassis 110. In particular, when the parcel carrier 200 is coupledto the UAV chassis 110, the upper portion 114 of the UAV chassis 110 maybe at least partially inserted into the cavity 272 of the upper portion271 of the receiving portion 270. The UAV chassis 110 may include theretaining members 120 (FIG. 7) that may selectively engage the receivingportion 270 to couple the parcel carrier 200 to the UAV chassis 110. Inthe embodiment depicted in FIG. 23B, the UAV electrical interface 130 ispositioned on the upper portion 114 of the UAV chassis 110 and thecarrier electrical interface 220 is positioned within the cavity 271 ofthe receiving portion 270 of the parcel carrier 200. The UAV electricalinterface 130 is positioned to align with the carrier electricalinterface 220 when the parcel carrier 200 is coupled to the UAV chassis110. Additionally, in the embodiment depicted in FIG. 23A, the landinggear 116 may be positioned on the upper portion 271 of the receivingportion 270, such that the landing gear are positioned on the parcelcarrier 200 as compared to the UAV chassis 110.

B. Primary Parcel Delivery Vehicle & UAV Support Mechanism

FIG. 24 illustrates a perspective view of the primary parcel deliveryvehicle 10. In the illustrated embodiment, the primary parcel deliveryvehicle is a stepvan (e.g., Workhorse Range-Extended E-Gen truck,Freightliner MT55, or the like). As shown in FIG. 24, the vehicle 10includes a roof panel 12, which supports a pair of UAV supportmechanisms 400. As explained in greater detail herein, the UAV supportmechanisms 400 are configured to enable a fleet of UAVs 100 to bedispatched from, and returned to, the vehicle 10 as part of a UAV-basedparcel delivery system. In the embodiment depicted in FIG. 24, thevehicle 10 includes two UAV support mechanisms 400, however, it shouldbe understood that the vehicle 10 may include a single UAV supportmechanism 400, or any suitable number of UAV support mechanisms 400 todispatch UAVs 100 (FIG. 1) from the vehicle 10.

As shown in FIG. 24, each UAV support mechanism 400 generally defines atakeoff end 402 and a landing region 404 that is positioned opposite thetakeoff end 402. In general, UAVs 100 (FIG. 1) may take off from thevehicle 10 from the takeoff end 402, and may return and land on thevehicle 10 at the landing region 404. In the embodiment depicted in FIG.24, the takeoff end 402 is positioned at the rear end of the vehicle 10,and the landing region 404 is positioned at the front end of the vehicle10, however, it should be understood that the takeoff end 402 may bepositioned at the front end of the vehicle 10 and the landing region 404may be positioned at the rear end of the vehicle 10. Additionally, insome embodiments, the takeoff end 402 and the landing region 404 of thesupport mechanism may be positioned at the same end of the vehicle 10.While the embodiments described herein include one or more UAV supportmechanisms 400 positioned on a vehicle 10, it should be understood thatUAV support mechanisms 400 may be provided on, and may be utilized todispatch UAVs 100 from, any suitable structure, for example, astationary building, structure, movable cargo pod, and/or the like.

Referring to FIG. 25, a perspective view of the UAV support mechanisms400 on the roof panel 12 of the vehicle 10 are schematically depicted.Each of the UAV support mechanisms 400 include a pair of opposing rails410 that extend along the roof panel 12 of the vehicle 10, and theopposing rails 410 are configured to engage the UAV chassis 110 (FIG.4), as will be described in greater detail herein. The opposing rails410 are generally symmetrical to one another, and extend along the roofpanel 12 in the longitudinal direction. Between the landing region 404and the takeoff end 402, the UAV support mechanisms 400 define a returnregion 406, a transport region 407, and a supply region 408.

The roof panel 12 of the vehicle 10 generally defines portals oropenings through which an interior compartment 18 of the vehicle 10 maybe accessed. In particular, in the embodiment depicted in FIG. 25, theroof panel 12 defines a return portal 14 and a supply portal 16. Thereturn portal 14 is positioned within the return region 406 of theopposing rails 410 and the supply portal 16 is positioned within thesupply region 408 of the opposing rails 410. In operation, when a UAV100 (FIG. 1) is engaged with the opposing rails 410, an empty parcelcarrier 200 (FIG. 2) may be released from the UAV chassis 110 (FIG. 2)and may be deposited within the interior compartment 18 of the vehicle10 through the return portal 14. A new parcel carrier 200 and parcel 300(FIG. 9) may be provided to the UAV chassis 110 (FIG. 3) from theinterior compartment 18 of the vehicle 10 through the supply portal 16,as will be described in greater detail herein.

Referring to FIG. 26A, a section view of the UAV support mechanism 400is schematically depicted along section 26A-26A of FIG. 25. As describedabove, the UAV support mechanism 400 includes the opposing rails 410that extend along the roof panel 12 in the longitudinal direction. Theopposing rails 410 are coupled to a plurality of support arms 416 thatextend upward from the roof panel 12 and the opposing rails 410 arepositioned above the roof panel 12 in the vertical direction. Bypositioning the opposing rails 410 above the roof panel 12 in thevertical direction, a parcel 300 (FIG. 9) may pass beneath the opposingrails 410 when the parcel 300 is coupled to a UAV chassis 110 (FIG. 2),as will be described in greater detail herein.

Referring collectively to FIGS. 25-26B a perspective view and sectionviews of the return region 406, the transport region 407, and the supplyregion 408 are schematically depicted. In the return region 406, thetransport region 407, and the supply region 408, the UAV supportmechanism 406 includes a conveyor 440 that is configured to move a UAV100 (FIG. 1) along the opposing rails 410 between the return region 406and the supply region 408. The conveyor 440 generally includes aplurality of rollers 442 that are positioned within a c-shaped profile410 a of the opposing rails 410. The c-shaped profile 410 a generallydefines an upper rail surface 412 that is oriented to face upward in thevertical direction and a lower rail surface 414 that is oriented to facedownward in the vertical direction. The upper rail surface 412 and thelower rail surface 414 may engage the upper portion 114 and the lowerportion 118 of the UAV chassis 110 (FIG. 2), restricting movement of theUAV chassis 110 in the vertical direction, as will be described ingreater detail herein. In some embodiments, the upper rail surface 412may include a communication connection that may be communicativelycoupled to the UAV computing entity 808 when the UAV chassis 110 is inthe UAV support mechanism 400, allowing notifications/messages to besent and received from the UAV computing entity 808 to a vehiclecomputing entity 810, as will be described in greater detail herein.

The rollers 442 rotate with respect to the c-shaped profile 410 a andmay engage the UAV chassis 110 (FIG. 2) to move the UAV chassis 110 fromthe supply region 408 to the return region 406. In embodiments, therollers 442 may be operatively coupled to a belt 444 that causes therollers 442 to rotate about a roller axis 445. The belt 444 may beoperatively coupled to a conveyor controller 460 that selectively movesthe belt 444 to rotate the plurality of rollers 442.

In embodiments, the conveyor 440 further includes a plurality ofincludes a plurality position sensors 450 positioned along the opposingrails 410. The position sensors 450 are configured to detect theposition of a UAV chassis 110 (FIG. 2) on the conveyor 440, and mayinclude a plurality of proximity sensors, such as capacitive sensors,inductive sensors, hall-effect sensors, and/or the like. The positionsensors 450 are communicatively coupled to the conveyor controller 460and may send signals to the conveyor controller 460, such as signalsindicative of a UAV chassis 110 (FIG. 2) being positioned proximate toone or more of the position sensors 450. In embodiments, the positionsensors 450 include a supply position sensor 450 a positioned within thesupply region 408 and a return position sensor 450 b positioned withinthe return region 406. The supply position sensor 450 a is configured todetect when the UAV chassis 110 (FIG. 2) is positioned over the supplyportal 16. Similarly, the return position sensor 450 b is configured todetect when the UAV chassis 110 (FIG. 2) is positioned over the returnportal 14.

Referring to FIG. 27, the conveyor controller 460 is schematicallydepicted. The conveyor controller 460 generally includes one or moreprocessing elements/components 462, a motor 464, and one or morecommunications elements/components 466. The motor 464 of the conveyorcontroller 460 may be operatively coupled to the belt 444 (FIG. 26B)such that the motor 464 drives the belt 444. The conveyor controller mayalso be communicatively coupled to the plurality of position sensors 450and may be communicatively coupled to one or more computing entities viathe communications device 466. In particular, the communications device466 is configured for communicating with various computing entities,such as by communicating information/data, content, information, and/orsimilar terms used herein interchangeably that can be transmitted,received, operated on, processed, displayed, stored, and/or the like.Such communication may be executed using a wired data transmissionprotocol, such as FDDI, DSL, ATM, frame relay, DOCSIS, or any otherwired transmission protocol. Similarly, the central computing entity 802may be configured to communicate via wireless external communicationnetworks using any of a variety of protocols, such as GPRS, UMTS,CDMA2000, 1×RTT, WCDMA, GSM, EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA,HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR protocols, NFC protocols,Wibree, Bluetooth protocols, wireless USB protocols, and/or any otherwireless protocol.

Referring to FIG. 28, a front view of the landing region 404 of the UAVsupport mechanism 400 is schematically depicted. The opposing rails 410converge in the lateral direction moving from the landing region 404 tothe return region 406 and a width between the opposing rails 410 isgreater in the landing region 410 as compared to the return region 406and the transport region 407. By converging in the lateral direction,the opposing rails 410 may assist in guiding the UAV chassis 110 (FIG.2) as the UAV 100 (FIG. 1) lands to the vehicle 10. Each of the opposingrails 410 include a damper 420 positioned at the landing region 404 ofthe opposing rails 410. The damper 410 generally includes flexiblebrushes 422 that elastically deform when contacted by a UAV chassis 110(FIG. 2). In particular, as a UAV 100 lands to the vehicle 10, movingalong the landing region 404 to the return region 406, the UAV chassis110 (FIG. 2) contacts the damper 410. As the UAV chassis 110 (FIG. 2)contacts the damper 410, the forward motion (e.g., motion in they-direction) of the UAV 100 (FIG. 1) will be slowed by the damper 410.

Referring to FIGS. 28 and 29, in embodiments the opposing rails 410 maybe moveable in the vertical direction and/or the lateral direction atthe landing region 404. In particular, the opposing rails 410 may beoperatively coupled a power source, such as a hydraulic pump and/or thelike that allows the landing to move in the vertical direction and/orthe lateral direction. By moving the opposing rails 410 in the verticaland/or the lateral direction, the opposing rails 410 may move to match aroute/flight path of a UAV 100, such that the UAV 100 may land to theopposing rails 410. In some embodiments, the opposing rails 410 at thelanding region 404 are hingedly coupled to the vehicle 10 and/or theconveyor 440 at hinges 441.

Referring again to FIG. 28, the opposing rails 410 include a guidancearray 430 positioned in the landing region 404. The guidance array 430generally includes various devices that may assist in guiding a UAV 100(FIG. 1) to land on the vehicle 10. In the embodiment depicted in FIG.28, the guidance array 430 includes a visual indicator 432 and apositioning beacon 434. Each of the opposing rails 410 include a visualindicator 432, which may include a light, LED, and/or the like thatemits a light (e.g., radiation on the visual spectrum), which may bedetected by the vehicle landing sensors 164 and/or the cameras 168 (FIG.10) to assist the UAV 100 (FIG. 1) in accurately locating the UAVsupport mechanism 400 when landing to the vehicle 10, as will bedescribed in greater detail herein.

The positioning beacon 434 may emit a signal that may be detected by thevehicle landing sensors 164 (FIG. 10) to assist the UAV 100 (FIG. 1) inaccurately locating the UAV support mechanism 400 when landing to thevehicle 10. In embodiments, the positioning beacon 434 may include suchtechnologies may include iBeacons, Gimbal proximity beacons, BLEtransmitters, Near Field Communication (NFC) transmitters, and/or thelike. While the embodiment depicted in FIG. 28 includes a positioningbeacon 434 positioned on each of the opposing rails 410, it should beunderstood that the positioning beacon 434 may include a single beaconor any suitable number of beacons positioned at any suitable location onthe opposing rails 410 to assist the UAV 100 (FIG. 1) in accuratelocating the UAV support mechanism 400.

i. Vehicle

Referring to FIG. 29, a rear perspective of the vehicle 10 isschematically depicted with certain panels removed for clarity. Asdescribed above, the vehicle 10 includes a pair of UAV supportmechanisms 400 positioned on the roof panel 12 of the vehicle 10.Positioned within the interior of the vehicle 10 is one or more parcelcarrier support racks 30. The racks 30 support multiple parcel carriers200 (FIG. 9), as will be described in greater detail herein. Two loadingrobots 500 are positioned within the interior compartment 18 of thevehicle 10. The loading robots 500 assist in moving parcel carriers 200(FIG. 9) within the interior compartment 18 of the vehicle 10, and eachof the loading robots 500 may be associated with one of the UAV supportmechanisms 400. The racks 30 are generally positioned along the sides ofthe vehicle 10, however, the racks 30 may be positioned at any suitablelocation within the vehicle 10, and racks 30 may be centrally positionedwithin the vehicle 10.

Referring to FIGS. 29 and 35A, the rear perspective of the vehicle 10and an enlarged perspective view of one of the racks 30 is shown,respectively. The racks 30 each include outwardly extending arms 32 thatextend outward from a base portion 31 of the rack 30. The racks 30further include a plurality of flange ends 34 that extend upward fromthe outwardly extending arms 32. The outwardly extending arms 32 and theflange ends 34 of the racks 30 are configured to engage the engagementhousing 210 of the parcel carrier 200 and restrain movement of theengagement housing 210 in the lateral and the longitudinal directions.In some embodiments, the racks 30 may also include one or moreelectrical contacts that may provide electrical charge to the powersupply 214 when the engagement housing 210 is positioned in the racks30, such that the power supply 214 may charge or re-charge when placedwithin the racks 30. By charging the power supplies 214, the racks 30may assist in preparing a parcel carrier 200 with an expended powersupply 214 for re-use.

Referring to FIG. 30, a perspective view of the vehicle 10 is depictedwith the racks 30 removed for clarity. The vehicle 10 includes twoloading robots 500, each of which are associated with a UAV supportmechanism 400 (FIG. 29). The loading robots 500 are each movable along ahorizontal track 502 that extends along the interior of the vehicle 18in the longitudinal direction. The loading robots 500 each include anupright member 504 operatively coupled to the horizontal track 502, andan end effector 510 coupled to the upright member 504. The uprightmember 504 extends upward in the vertical direction and generallydefines a vertical track 506 extending along the upright member 504 inthe vertical direction. The end effector 510 is movable along theupright member 504 in the vertical direction along the vertical track504. Each of the robots 500 include a parcel identification unit 511that is configured to scan, read, interrogate, receive, communicatewith, and/or similar words used herein interchangeably a parcelidentifier and/or a parcel carrier identifier, and the parcelidentification unit 511 may be communicatively coupled to one or morecomputing entities, as will be described in greater detail herein.

Referring collectively to FIGS. 35A, 35B, and 35C, a perspective view ofthe end effector 510 is schematically depicted. The end effector 510includes an end effector track 514, a platform 512 positioned on andmovable along the end effector track 514, and clamping members 516positioned on opposing ends of the platform 512. The platform 512 maygenerally support the parcel 300 and the clamping members 516 may berepositionable between an engaged position, in which the clampingmembers 516 contact opposing sides of the parcel 300, and a disengagedposition, in which the clamping members 516 are spaced apart from thesides of the parcel 300. The clamping members 516 may retain theposition of the parcel 300 on the platform 512 of the end effector 510when the loading robot 500 moves the parcel 300 within the interiorcompartment 18 of the vehicle 10. In the embodiment depicted in FIGS.35A, 35B, and 35C, the clamping members 516 are positioned on opposingends of the platform 512 in the longitudinal direction, however, itshould be understood that the clamping members 516 may be positioned atany suitable location of the end effector 510 to retain the position ofthe parcel 300 with respect to the platform 512 of the end effector 510.The clamping members 516 may be repositionable between the engagedposition and the disengaged position in any suitable manner, including,but not limited to, electrical power, hydraulic power, and/or the like.

The platform 512 of the end effector 510 is also movable with respect tothe upright member 504 in the lateral direction along the end effectortrack 514. Accordingly, the loading robots 500 are moveable within theinterior compartment 18 of the vehicle 10 in the longitudinal direction(e.g., along the horizontal track 502), in the vertical direction (e.g.,along the vertical track 504), and in the lateral direction (e.g., alongthe end effector track 514). While the loading robots 500 are generallydescribed herein as including three-axis robots, it should be understoodthat the loading robots 500 may include any suitable robot to moveparcel carriers 200 (FIG. 9) within the interior compartment 18 of thevehicle, such as a six-axis robot, and/or the like.

Referring to FIG. 31, a schematic diagram of a loading robot controller520 is schematically depicted. The loading robot controller 520 iscommunicatively coupled to various components of the loading robot 500and generally controls the movement and function of the loading robot500. The loading robot controller 520 generally includes one or moreloading robot processing elements/components 522, one or more memoryelements/components 521, and one or more loading robot communicationselements/components 524. In embodiments, the loading robot controller520 may be communicatively coupled to the conveyor controller 460 and/orto the positioning sensors 450 of the UAV support mechanism 400 suchthat the operation of the robot may be initiated based on signalsreceived from the conveyor controller 460 and/or the positioning sensors450. For example the loading robot controller 520 may initiate movementof the robot 500 when a UAV chassis 110 is detected over the supplyportal 16 or the return portal 14, as will be described in greaterdetail herein. The communications device 524 is configured forcommunicating with various computing entities, such as by communicatinginformation/data, content, information, and/or similar terms used hereininterchangeably that can be transmitted, received, operated on,processed, displayed, stored, and/or the like. Such communication may beexecuted using a wired data transmission protocol, such as FDDI, DSL,ATM, frame relay, DOCSIS, or any other wired transmission protocol.Similarly, the central computing entity 802 may be configured tocommunicate via wireless external communication networks using any of avariety of protocols, such as GPRS, UMTS, CDMA2000, 1×RTT, WCDMA, GSM,EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct,WiMAX, UWB, IR protocols, NFC protocols, Wibree, Bluetooth protocols,wireless USB protocols, and/or any other wireless protocol.

ii. Loading Parcels/Parcel Carriers to Vehicle

Reference will now be made herein to the loading of parcels to thevehicle 10. As may be appreciated, a sender may send a parcel to aconsignee through a carrier. The carrier may transport the parcel to oneor more intermediate locations, such as processing centers and/orwarehouses, in the process of delivering the parcel to the consignee. Indelivery process involving UAVs, the parcels may be attached to a parcelcarrier prior to loading the parcel and parcel carrier to a vehicle, asdescribed below.

Referring to FIG. 32, a perspective view of a loading operation ofparcel carriers 200 to parcels 300 is schematically depicted. Anautomated parcel/parcel carrier connection system 600 is positionedwithin an intermediate location 601. The intermediate location 601 mayinclude a facility, such as a warehouse or distribution center, in whichparcels 300 are sorted and dispatched as part of a delivery process. Theconnection system 600 includes racks 610 in which parcel carriers 200are stored, a loading robot 612, a transport rail 620, a plurality ofparcel carrier clamps 622 positioned on the transport rail 620, aconveyor belt 630, and an engagement clamping mechanism 634 positionedon the conveyor belt 630. The racks 610 may be substantially similar tothe racks 30 described above and depicted in FIG. 29. In the embodimentdepicted in FIG. 32, the racks 610 may also provide electrical charge tothe parcel carriers 200, such as when the parcel carriers 200 includethe power supply 214. By providing electrical charge to the power supply214, the racks 610 may prepare individual parcel carriers 200 to delivera parcel 300 via a UAV 100 (FIG. 1).

The loading robot 612 is substantially similar to the robot 500 (FIG.30) positioned in the vehicle 10, and is configured to retrieve parcelcarriers 200 from the racks 610 and supply the retrieved parcel carriers200 to the transport rail 620. Similar to the robots 500 (FIG. 30), theloading robot 612 may include a three-axis robot, or may include anysuitable robot to move parcel carriers 200, such as a six-axis robot,and/or the like. The loading robot 612 may include a parcel carrieridentification unit 613 that is configured to scan, read, interrogate,receive, communicate with, and/or similar words used hereininterchangeably a parcel carrier identifier on each of the parcelcarriers 200 and that may be communicatively coupled to one or morecomputing entities. For example, the parcel carrier 200 may include aparcel carrier identifier, such as an alphanumeric identifier or machinereadable identifier. Such parcel carrier identifiers may be representedas text, barcodes, tags, character strings, Aztec Codes, MaxiCodes, DataMatrices, Quick Response (QR) Codes, electronic representations, and/orthe like. A unique parcel identifier (e.g., 123456789) may be used bythe carrier and may be associated with a parcel identifier and/or a UAVidentifier to identify and track the parcel carrier as it moves throughthe carrier's transportation network. Further, such parcel carrieridentifiers can be affixed to the parcel carriers by, for example, usinga sticker (e.g., label) with the unique parcel carrier identifierprinted thereon (in human and/or machine readable form) or an RFID tagwith the unique parcel identifier stored therein.

The plurality of parcel carrier clamps 622 are operatively coupled tothe transport rail 620, and the transport rail 620 may move the parcelcarrier clamps 622 along the transport rail 620 to attach parcelcarriers 200 to parcels 300 positioned on a conveyor belt 630. Inparticular, the loading robot 612 may insert a parcel carrier 200 toparcel carrier clamps 622 on the transport rail 620. The parcel carrierclamps 622 may be inwardly biased such that the parcel carrier 200 isretained within the parcel carrier clamps 622. The inward bias of theparcel carrier clamps 622 may be caused by a biasing member, such as atension spring, a torsion spring, a compression spring, and/or the like.

The parcel carrier clamps 622, along with parcel carriers 200 that areselectively coupled to the parcel carrier clamps 622 move along thetransport rail 620 toward the conveyor belt 630. In embodiments, theparcel carrier clamps 622 are positioned over the conveyor belt 630. Theparcel carrier clamps 622 move downward to the conveyor belt 630, wherethe parcel carriers 200 are engaged with parcels 300 positioned on theconveyor belt 630.

The parcel carrier clamps 622 move downward toward the conveyor belt 630at the engagement clamping mechanism 634. Upon reaching the engagementclamping mechanism 634, the engagement clamping mechanism 634 may matethe parcel carrier 200 to the parcel 300, such as by pressing the parcelcarrying arms 230 inward into the parcel 300. Once the parcel carrier200 is engaged with the parcel 300, the parcel carrier clamps 622 maydisengage with the parcel carrier 200, and continue moving along thetransport rail 620.

The parcel/parcel carrier connection system 600 may further include aparcel identification unit 632 that may communicate with a parcelidentifier of the parcels 300 that are positioned on the conveyor belt630. For example, each parcel 300 may include a parcel identifier, suchas an alphanumeric identifier or machine readable identifier. Suchparcel identifiers may be represented as text, barcodes, tags, characterstrings, Aztec Codes, MaxiCodes, Data Matrices, QR Codes, electronicrepresentations, and/or the like. A unique parcel identifier (e.g.,123456789) may be used by the carrier to identify and track the parcelas it moves through the carrier's transportation network. Further, suchparcel identifiers can be affixed to parcels by, for example, using asticker (e.g., label) with the unique parcel identifier printed thereon(in human and/or machine readable form) or an RFID tag with the uniqueparcel identifier stored therein.

The parcel identification unit 632 may include a barcode scanner, acomputer vision system, an RFID antenna and/or the like that isconfigured to read the parcel identifier of the parcel 300. The parcelidentification unit 632 may be communicatively coupled to one or morecomputing entities, and the parcel identification unit may communicateinformation/data associated with the parcel identifier of each parcel300 to the one or more computing entities, as will be described ingreater detail herein.

Referring to FIGS. 33 and 34, a perspective view of a vehicle 10 beingloaded with parcels 300 is schematically depicted. In embodiments, theparcels 300 and attached parcel carriers 200 may be conveyed into a rearopening of the vehicle 10 by a parcel conveyor 700. The parcel conveyor700 may include a conveyor belt, powered rollers, and/or the like thatmove parcels 300 and their attached parcel carriers 200 into the vehicle10. The parcel conveyor 700 may include a pusher mechanism 702 thatmoves parcels 300 and their attached parcel carriers 200 from the parcelconveyor 700 onto the end effector 510 of the loading robot 500. Inparticular, the pusher mechanism 702 may move the parcel 300 and itsattached parcel carrier 200 in the lateral direction, transferring theparcel 300 and parcel carrier 200 from the parcel conveyor 700 to theend effector 510 of the loading robot 500. Once the parcel 300 andparcel carrier 200 are positioned on the loading robot 500, the loadingrobot 500 moves the parcel 300 and the parcel carrier 200 to the rack 30positioned within the vehicle 10.

For example and referring to FIG. 35A, the loading robot 500 may movethe parcel 300 and the parcel carrier 200 proximate to an available pairof outwardly extending arms 32 of the rack 30 (e.g., a pair of outwardlyextending arms 32 that are not engaged with a parcel carrier 200/parcel300). The loading robot 500 may move the parcel 300 and attached parcelcarrier 200 in the vertical direction such that an underside of theparcel carrier 200 is generally aligned with the outwardly extendingarms 32 of the rack 30 in the vertical direction.

Referring to FIG. 35B, upon aligning the underside of the parcel carrier200 with the outwardly extending arms 32 of the rack 30, the platform512 of the loading robot 500 moves toward the outwardly extending arms32 in the lateral direction along the end effector track 514. Theloading robot 500 moves the platform 512 toward the outwardly extendingarms 32 until the outwardly extending arms 32 are positioned between theparcel carrier 200 and the parcel 300 in the vertical direction.

Referring to FIG. 35C, once the outwardly extending arms 32 arepositioned between the parcel carrier 200 and the parcel 300 in thevertical direction, the clamping members 516 of the end effector 510move from the engaged position to the disengaged position, such that theclamping members 516 are spaced apart from the parcel 300 in thelongitudinal direction. The parcel 300 and the parcel carrier 200 may besupported by the outwardly extending arms 32, and in particular, thebottom surface of the parcel carrier 200 may be positioned on theoutwardly extending arms 32 with the parcel 300 positioned below theoutwardly extending arms 32 in the vertical direction. Movement of theparcel carrier 200 and the parcel 300 with respect to the outwardlyextending arms 32 may be restricted by the flange ends 34.

Once the parcel 300 and the parcel carrier 200 are positioned on theoutwardly extending arms 32, the platform 512 moves along the endeffector track 514 towards the upright member 504 of the loading robot500, such that the loading robot 500 is prepared to retrieve anotherparcel 300 and parcel carrier 200 from the conveyor 700 (FIG. 34).

iii. Loading/Unloading to UAV Chassis

Once the vehicle 10 is loaded with parcels 300 their associated parcelcarriers 200, the vehicle 10 may be dispatched to deliver the parcels300, for example as part of a delivery route. When delivering theparcels 300, the UAVs 100 (FIG. 1) are loaded with parcels 300 and theirassociated parcel carriers 200, as described below.

Referring collectively to FIGS. 36 and 37, UAV chassis 110 arepositioned on the UAV support mechanisms 400 of the vehicle 10. Withinthe return region 406, the transport region 407, and the supply region408, the UAV support mechanism 400, the UAV chassis 110 are engaged withthe conveyor 440. In particular, the landing gear 116 contact and engagewith the upper surface 412 of the opposing rails 410, and the reducedwidth portion 115 of the UAV chassis 110 is positioned between theopposing rails 410 in the lateral direction. Furthermore, the upperportion 114 of the UAV chassis 110 is positioned above the opposingrails 410 and the lower portion 118 of the UAV chassis 110 is positionedbelow the opposing rails 410. In embodiments, the width of the upperportion 114 and the width of the lower portion 118 evaluated in thelateral direction are both greater than a width ‘w’ between the opposingrails 410 evaluated in the lateral direction. As the upper portion 114and the lower portion 118 of the UAV chassis 110 have a greater widththan the width between the opposing rails 410, the UAV chassis 110, theUAV chassis 110 is restrained in the vertical direction when positionedin the conveyor 440.

The conveyor 440 moves the UAV chassis 110, such as through the rollers442, (and/or the landing gear 116 when the landing gear 116 includespowered rollers) in the longitudinal direction through the transportregion 407 and into the supply region 408 of the conveyor 440. Once inthe supply region 408, the rollers 442 may stop rotating once the UAVchassis 110 is positioned over the supply portal 16. The conveyorcontroller 460 (FIG. 25) may detect when the UAV chassis 110 ispositioned over the supply portal 16, such as through the supplyposition sensor 450 a (FIG. 25). Once the UAV chassis 110 is positionedover the supply portal 16, a parcel 300 and attached parcel carrier 200may be retrieved from the interior compartment 18 of the vehicle 10 andattached to the UAV chassis 110 to load the UAV chassis 110 for flight.

Referring to FIG. 38A, to retrieve a parcel 300 and associated parcelcarrier 200 from the interior compartment 18 of the vehicle 10, theloading robot 500 positions the end effector 510 of the loading robot500 below a parcel 300 on the rack 30. In particular, the platform 512of the end effector 510 is positioned below the parcel 300, and theclamping members 516 may engage the sides of the parcel 300.

Referring to FIG. 38B, with the end effector 510 engaged with the parcel300, the loading robot 500 lifts the parcel 300 and the attached parcelcarrier 200 upward in the vertical direction, such that the parcelcarrier 200 is disengaged from the rack 30.

Referring to FIG. 38C, the loading robot 500 then moves the parcel 300and attached parcel carrier 200 away from the rack 30, and moves theparcel 300 and attached parcel carrier 200 toward the supply portal 16.The loading robot 500 positions the parcel 300 and the parcel carrier200 under the UAV chassis 110 such that the parcel carrier 200 may beinserted within the lower portion 118 of the UAV chassis 110. Theloading robot 500 moves upward in the vertical direction and inserts theparcel carrier 200 within the lower portion 118 of the UAV chassis 110,and the parcel carrier 200 may be retained within the lower portion 118,such as by the retaining members 120 (FIG. 7). Upon inserting the parcelcarrier 200 within the lower portion 118 of the UAV chassis 110, theclamping members 516 of the end effector 510 move into the disengagedposition, and the end effector 510 may separate from the parcel 300.

Referring to FIG. 39, once the parcel 300 and the parcel carrier 200 areselectively coupled to the UAV chassis 110, the UAV 100 is prepared todeliver the parcel 300 to a destination, and the conveyor 440 moves theUAV 100 from the supply region 408 to the takeoff end 402. Once at thetakeoff end 402, the propulsion members 102 of the UAV 100 may power up,and the propellers 103 of the propulsion members 102 begin to rotatesuch that the UAV 100 may take off from the takeoff end 402 to deliverthe parcel 300 to a destination.

As will be described in greater detail herein, the UAV 100 may deliverthe parcel 300 to a destination at a serviceable point 5901. Uponsuccessful delivery of the parcel 300 to the destination at aserviceable point 5901, the UAV 100 returns to the vehicle 10 with theempty parcel carrier 200, where it may be re-supplied with anotherparcel 300 and parcel carrier 200. As will be recognized, the UAV 100may also pick up one or more parcels 300 after delivery of one or moreparcels 300 at one or more serviceable points 5901 (e.g., a multi-stoppick-up and/or delivery).

Referring to FIG. 40, a UAV 100 is depicted initiating a landing on thevehicle 10, such as when the UAV 100 is returning to the vehicle 10after successful delivery of a parcel 300. In embodiments, the vehiclelanding sensors 164 of the UAV 100 detect one or more components of theguidance array 430 such that the UAV 100 may locate the opposing rails410 of the UAV support system 400. For example in some embodiments, thevehicle landing sensors 164 may detect the position of the visualindicator 432 and/or the positioning beacon 434 of the UAV supportmechanism 400. By detecting the position of the visual indicator 432and/or the positioning beacon 434, the vehicle landing sensors 164 mayprovide the UAV 100 with an accurate estimate of the position of theopposing rails 410 such that the UAV 100 may navigate toward the landingregion 404 of the opposing rails 410.

In various embodiments, the UAV 100 may be configured to only land onthe vehicle 10 while the vehicle 10 is stopped. For example, forhuman-operated vehicles, the UAV 100 may be incapable of predicting themovement of the vehicle 10, and accordingly the UAV 100 may only land tothe UAV support mechanism 400 when the movement of the vehicle 10 can beaccurately predicted, such as when the vehicle 10 is stationary. In suchembodiments, the UAVs 100 may be configured to follow the vehicle 10 ata predetermined distance while it moves until the vehicle 10 comes to astop.

In various embodiments, the UAV 100 may be configured to land on thevehicle 10 when the vehicle 10 is in motion. For example, when thevehicle 10 includes an autonomous vehicle, the vehicle 10 maypredictably move along a predetermined/configurable route, such that themovement of the vehicle 10 can be accurately predicted. In theseembodiments, the UAV 100 may land on the vehicle 10 while the vehicle 10is in motion.

Referring to FIG. 41, a perspective view of the UAV 100 landing on theUAV support mechanism 400. Upon accurately locating the opposing rails410, such as through the guidance array 430, the UAV 100 navigates suchthat the upper portion 114 of the UAV chassis 110 is positioned abovethe opposing rails 410 and the lower portion 118 of the UAV chassis 110is positioned below the opposing rails 410 in the vertical direction.The tapered shape of the upper portion 114 and the lower portion 118 ofthe UAV chassis 110 may assist in guiding the UAV 100 such that theupper portion 114 is positioned above the opposing rails 410 and thelower portion 118 is positioned below the opposing rails 410. With theupper portion 114 positioned above the opposing rails 410 and the lowerportion 118 positioned below the opposing rails 410, the UAV 100 movesrearward in the longitudinal direction as the opposing rails 410converge in the lateral direction. The UAV 100 may move rearward in thelongitudinal direction under the power of the propulsion members 102until the UAV 100 reaches the conveyor 440 positioned rearward of thelanding region 404.

Once the UAV 100 has landed to the UAV support mechanism 400 and hasengaged with the conveyor 440, the propulsion members 102 of the UAV maypower down, such that the propellers 103 stop rotating. The conveyor 440then may move the UAV 100 to the return region 406.

Referring to FIG. 42A, the conveyor 440 moves the UAV 100 to the returnportal 14. The conveyor controller 460 (FIG. 25) may detect when the UAVchassis 110 is positioned over the return portal 14, such as through thereturn position sensor 450 b (FIG. 25). At the return portal 14, theloading robot 500 may engage the now empty parcel carrier 200 with theend effector 510, and the parcel carrier 200 may be selectivelyde-coupled from the UAV chassis 110. Upon the parcel carrier 200 beingde-coupled from the UAV chassis 110, the loading robot 500 may lower theend effector 510, and accordingly the parcel carrier from the UAVchassis 110.

Referring to FIG. 42B, the loading robot 500 may position the emptyparcel carrier 200 from the UAV chassis 110 to the rack 30 within theinterior compartment 18 of the vehicle 10. With the empty parcel carrier200 removed from the UAV chassis 110, the conveyor 440 moves the UAVchassis 110 from the return region 406, and through the transport region407 to the supply region 408 (FIG. 36), where the UAV chassis 110 may bere-supplied with a new parcel carrier 200 and parcel 300, as describedabove.

Referring now to FIG. 43, a perspective view of an alternative interiorcompartment 18 of the vehicle 10 is schematically depicted. In theembodiment depicted in FIG. 43, the interior compartment 18 of thevehicle 10 includes the racks 30 for use with the parcel carriers 200(FIG. 17) configured to be delivered by UAV 100 (FIG. 1), as well asracks 41 for conventional parcels 300 that may be delivered manually bya delivery employee. In particular, in such embodiments, the vehicle 10may deliver parcels 300 via UAV 100, while simultaneously deliveringparcels 300 through conventional methods (e.g., by a delivery employee).

Referring to FIG. 44 a perspective view of an alternative vehicle 10 isschematically depicted. In the embodiment depicted in FIG. 44, thevehicle 10 includes a trailer, such as a trailer that may be selectivelycoupled to a semi-truck. The vehicle 10 includes the UAV supportmechanism 400 as described above from which the UAVs 100 may take offand land, and may include one or more robots configured to load andunload parcel carriers 200 from the UAVs 100. In such embodiments, thevehicle 10 may be moved to a certain location to deliver parcels 300 andmay remain stationary at that location while the UAVs 100 deliverparcels 300 from the vehicle 10. The vehicle 10 may remain in place atthe location while the UAVs 100 deliver the parcels 300 from the vehicle10 until all of the parcels 300 have been delivered from the vehicle 10,or until a delivery has been attempted for each of the parcels 300within the vehicle 10, at which time the vehicle 10 may be picked up andreturned to a serviceable point 5901. Such vehicles may assist indelivering parcels 300 during periods of high-volume, such as duringholiday delivery season, supplementing other delivery methods.

Referring to FIGS. 45A and 45B, another embodiment of vehicles 10 areschematically depicted. In the embodiment depicted in FIGS. 45A and 45B,the UAV support mechanism 400 includes a landing pad 40 positioned onthe roof panel 12 of the vehicle 10. In such embodiments, the UAVs 100may land to landing pad 40, as compared to the UAV support mechanism 400described above. The landing pad 40 is configured to support the UAV100, and includes a portal through which the interior compartment 180 ofthe vehicle 10 may be accessed. The vehicle 10 may include the robots500 (FIG. 30) and the racks 30 (FIG. 29), and may be similarlyconfigured to provide parcel carriers 200 to the UAV 100 at the landingpad 40, as compared to the supply portal 16 and the return portal 14, asdescribed above.

Reference will now be made to the interconnectivity of variouscomponents of the enhanced parcel delivery system.

3. Computer Program Products, Methods, and Computing Entities

Embodiments described herein may be implemented in various ways,including as computer program products that comprise articles ofmanufacture. Such computer program products may include one or moresoftware elements/components including, for example, software objects,methods, data structures, and/or the like. A software component may becoded in any of a variety of programming languages. An illustrativeprogramming language may be a lower-level programming language such asan assembly language associated with a particular hardware architectureand/or operating system platform. A software component comprisingassembly language instructions may require conversion into executablemachine code by an assembler prior to execution by the hardwarearchitecture and/or platform. Another example programming language maybe a higher-level programming language that may be portable acrossmultiple architectures. A software component comprising higher-levelprogramming language instructions may require conversion to anintermediate representation by an interpreter or a compiler prior toexecution.

Other examples of programming languages include, but are not limited to,a macro language, a shell or command language, a job control language, ascript language, a database query or search language, and/or a reportwriting language. In one or more example embodiments, a softwarecomponent comprising instructions in one of the foregoing examples ofprogramming languages may be executed directly by an operating system orother software component without having to be first transformed intoanother form. A software component may be stored as a file or other datastorage construct. Software elements/components of a similar type orfunctionally related may be stored together such as, for example, in aparticular directory, folder, or library. Software elements/componentsmay be static (e.g., pre-established or fixed) or dynamic (e.g., createdor modified at the time of execution).

A computer program product may include a non-transitorycomputer-readable storage medium storing applications, programs, programmodules, scripts, source code, program code, object code, byte code,compiled code, interpreted code, machine code, executable instructions,and/or the like (also referred to herein as executable instructions,instructions for execution, computer program products, program code,and/or similar terms used herein interchangeably). Such non-transitorycomputer-readable storage media include all computer-readable media(including volatile and non-volatile media).

In one embodiment, a non-volatile computer-readable storage medium mayinclude a floppy disk, flexible disk, hard disk, solid-state storage(SSS) (e.g., a solid state drive (SSD), solid state card (SSC), solidstate module (SSM), enterprise flash drive, magnetic tape, or any othernon-transitory magnetic medium, and/or the like. A non-volatilecomputer-readable storage medium may also include a punch card, papertape, optical mark sheet (or any other physical medium with patterns ofholes or other optically recognizable indicia), compact disc read onlymemory (CD-ROM), compact disc-rewritable (CD-RW), digital versatile disc(DVD), Blu-ray disc (BD), any other non-transitory optical medium,and/or the like. Such a non-volatile computer-readable storage mediummay also include read-only memory (ROM), programmable read-only memory(PROM), erasable programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), flash memory (e.g.,Serial, NAND, NOR, and/or the like), multimedia memory cards (MMC),secure digital (SD) memory cards, SmartMedia cards, CompactFlash (CF)cards, Memory Sticks, and/or the like. Further, a non-volatilecomputer-readable storage medium may also include conductive-bridgingrandom access memory (CBRAM), phase-change random access memory (PRAM),ferroelectric random-access memory (FeRAM), non-volatile random-accessmemory (NVRAM), magnetoresistive random-access memory (MRAM), resistiverandom-access memory (RRAM), Silicon-Oxide-Nitride-Oxide-Silicon memory(SONOS), floating junction gate random access memory (FJG RAM),Millipede memory, racetrack memory, and/or the like.

In one embodiment, a volatile computer-readable storage medium mayinclude RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM,cache memory, register memory, and/or the like. It will be appreciatedthat where embodiments are described to use a computer-readable storagemedium, other types of computer-readable storage media may besubstituted for or used in addition to the computer-readable storagemedia described above.

As should be appreciated, various embodiments of the present inventionmay also be implemented as methods, apparatus, systems, computingdevices, computing entities, and/or the like. As such, embodiments ofthe present invention may take the form of an apparatus, system,computing device, computing entity, and/or the like executinginstructions stored on a computer-readable storage medium to performcertain steps or operations. Thus, embodiments of the present inventionmay also take the form of an entirely hardware embodiment, an entirelycomputer program product embodiment, and/or an embodiment that comprisescombination of computer program products and hardware performing certainsteps or operations.

Embodiments of the present invention are described below with referenceto block diagrams and flowchart illustrations. Thus, it should beunderstood that each block of the block diagrams and flowchartillustrations may be implemented in the form of a computer programproduct, an entirely hardware embodiment, a combination of hardware andcomputer program products, and/or apparatus, systems, computing devices,computing entities, and/or the like carrying out instructions,operations, steps, and similar words used interchangeably (e.g., theexecutable instructions, instructions for execution, program code,and/or the like) on a computer-readable storage medium for execution.For example, retrieval, loading, and execution of code may be performedsequentially such that one instruction is retrieved, loaded, andexecuted at a time. In some exemplary embodiments, retrieval, loading,and/or execution may be performed in parallel such that multipleinstructions are retrieved, loaded, and/or executed together. Thus, suchembodiments can produce specifically-configured machines performing thesteps or operations specified in the block diagrams and flowchartillustrations. Accordingly, the block diagrams and flowchartillustrations support various combinations of embodiments for performingthe specified instructions, operations, or steps.

4. Exemplary System Architecture

FIG. 46 provides an illustration of an exemplary embodiment of thepresent invention. As shown in FIG. 46, this particular embodiment mayinclude one or more central computing entities 802, one or more networks800, one or more user computing entities 804, one or more mobile carriercomputing entities 806, one or more UAV computing entities 808, one ormore parcel carrier computing entities 212, one or more delivery vehiclecomputing entities 810, and/or the like. Each of these components,entities, devices, systems, and similar words used hereininterchangeably may be in direct or indirect communication with, forexample, one another over the same or different wired or wirelessnetworks. Additionally, while FIG. 43 illustrates the various systementities as separate, standalone entities, the various embodiments arenot limited to this particular architecture.

A. Exemplary Central Computing Entity

FIG. 47 provides a schematic of a central computing entity 802 accordingto one embodiment of the present invention. The central computing entity802 can be operated by a variety of entities, including carriers. Aswill be recognized, a carrier may be a traditional carrier, such asUnited Parcel Service (UPS), FedEx, DHL, courier services, the UnitedStates Postal Service (USPS), Canadian Post, freight companies (e.g.truck-load, less-than-truckload, rail carriers, air carriers, oceancarriers, etc.), and/or the like. However, a carrier may also be anontraditional carrier, such as Coyote, Amazon, Google, Airbus, Uber,ride-sharing services, crowd-sourcing services, retailers, and/or thelike.

As indicated, in one embodiment, the central computing entity 802 mayalso include one or more communications elements/components 908 forcommunicating with various computing entities, such as by communicatinginformation/data, content, information, and/or similar terms used hereininterchangeably that can be transmitted, received, operated on,processed, displayed, stored, and/or the like.

As shown in FIG. 47, in one embodiment, the central computing entity 802may include or be in communication with one or more processingelements/components 902 (also referred to as processors, processingcircuitry, processing device, and/or similar terms used hereininterchangeably) that communicate with other elements/components withinthe central computing entity 802 via a bus, for example. As will beunderstood, the processing elements/components 902 may be embodied in anumber of different ways. For example, the processing element/component902 may be embodied as one or more CPLDs, “cloud” processors,microprocessors, multi-core processors, coprocessing entities, ASIPs,microcontrollers, and/or controllers. Further, the processingelement/component 902 may be embodied as one or more other processingdevices or circuitry. The term circuitry may refer to an entirelyhardware embodiment or a combination of hardware and computer programproducts. Thus, the processing element/component 902 may be embodied asintegrated circuits, ASICs, FPGAs, PLAs, hardware accelerators, othercircuitry, and/or the like. As will therefore be understood, theprocessing element/component 902 may be configured for a particular useor configured to execute instructions stored in volatile or non-volatilemedia or otherwise accessible to the processing element/component 902.As such, whether configured by hardware or computer program products, orby a combination thereof, the processing element/component 902 may becapable of performing steps or operations according to embodiments ofthe present invention when configured accordingly.

In one embodiment, the central computing entity 802 may further includeor be in communication with memory components/elements—such asnon-volatile media (also referred to as non-volatile storage, memory,memory storage, memory circuitry and/or similar terms used hereininterchangeably). In one embodiment, the non-volatile storage or memorymay include one or more non-volatile storage or memory media 904,including but not limited to hard disks, ROM, PROM, EPROM, EEPROM, flashmemory, MMCs, SD memory cards, Memory Sticks, CBRAM, PRAM, FeRAM, NVRAM,MRAM, RRAM, SONOS, FJG RAM, Millipede memory, racetrack memory, and/orthe like. As will be recognized, the non-volatile storage or memorymedia may store databases, database instances, database managementsystems, information/data, applications, programs, program modules,scripts, source code, object code, byte code, compiled code, interpretedcode, machine code, executable instructions, and/or the like. The termdatabase, database instance, database management system, and/or similarterms used herein interchangeably may refer to a collection of recordsor data that is stored in a computer-readable storage medium using oneor more database models, such as a hierarchical database model, networkmodel, relational model, entity-relationship model, object model,document model, semantic model, graph model, and/or the like.

In one embodiment, the memory components/elements may further include orbe in communication with volatile media (also referred to as volatilestorage, memory, memory storage, memory circuitry and/or similar termsused herein interchangeably). In one embodiment, the volatile storage ormemory may also include one or more volatile storage or memory media906, including but not limited to RAM, DRAM, SRAM, FPM DRAM, EDO DRAM,SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM,RIMM, DIMM, SIMM, VRAM, cache memory, register memory, and/or the like.As will be recognized, the volatile storage or memory media may be usedto store at least portions of the databases, database instances,database management systems, information/data, applications, programs,program modules, scripts, source code, object code, byte code, compiledcode, interpreted code, machine code, executable instructions, and/orthe like being executed by, for example, the processingelement/component 902. Thus, the databases, database instances, databasemanagement systems, information/data, applications, programs, programmodules, scripts, source code, object code, byte code, compiled code,interpreted code, machine code, executable instructions, and/or the likemay be used to control certain aspects of the operation of the centralcomputing entity 802 with the assistance of the processingelement/component 902 and operating system.

As indicated, in one embodiment, the central computing entity 802 mayalso include one or more communications components/elements 908 forcommunicating with various computing entities, such as by communicatinginformation/data, content, information, and/or similar terms used hereininterchangeably that can be transmitted, received, operated on,processed, displayed, stored, and/or the like. Such communication may beexecuted using a wired data transmission protocol, such as FDDI, DSL,ATM, frame relay, DOCSIS, or any other wired transmission protocol.Similarly, the central computing entity 802 may be configured tocommunicate via wireless external communication networks using any of avariety of protocols, such as GPRS, UMTS, CDMA2000, 1×RTT, WCDMA, GSM,EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct,WiMAX, UWB, IR protocols, NFC protocols, Wibree, Bluetooth protocols,wireless USB protocols, and/or any other wireless protocol.

Although not shown, the central computing entity 802 may include or bein communication with one or more input components/elements, such as akeyboard input, a mouse input, a touch screen/display input, motioninput, movement input, audio input, pointing device input, joystickinput, keypad input, and/or the like. The central computing entity 802may also include or be in communication with one or more outputelements/components (not shown), such as audio output, video output,screen/display output, motion output, movement output, and/or the like.

As will be appreciated, one or more of the central computing entity's802 elements/components may be located remotely from other centralcomputing entity 802 components/elements, such as in a distributedsystem. That is, the term “central” is used in the generic sense and isnot intended to necessarily indicate a central location. Furthermore,one or more of the elements/components may be combined and additionalelements/components performing functions described herein may beincluded in the central computing entity 802. Thus, the centralcomputing entity 802 can be adapted to accommodate a variety of needsand circumstances. As will be recognized, these architectures anddescriptions are provided for exemplary purposes only and are notlimiting to the various embodiments.

B. Exemplary User Computing Entity

A user may be an individual, a family, a company, an organization, anentity, a department within an organization, a representative of anorganization and/or person, and/or the like. Thus, as will berecognized, in certain embodiments, users may be consignors and/orconsignees. To do so, a user may operate a user computing entity 804that includes one or more elements/components that are functionallysimilar to those of the central computing entity 802.

FIG. 48 provides an illustrative schematic representative of a usercomputing entity 804 that can be used in conjunction with embodiments ofthe present invention. In general, the terms device, system, computingentity, entity, and/or similar words used herein interchangeably mayrefer to, for example, one or more computers, computing entities,desktop computers, mobile phones, tablets, phablets, notebooks, laptops,distributed systems, smart home entities, kitchen appliances, GoogleHome, Amazon Echo, garage door controllers, cameras, imaging devices,thermostats, security systems, networks, gaming consoles (e.g., Xbox,Play Station, Wii), watches, glasses, iBeacons, proximity beacons, keyfobs, RFID tags, ear pieces, scanners, televisions, dongles, cameras,wristbands, wearable items/devices, items/devices, vehicles, kiosks,input terminals, servers or server networks, blades, gateways, switches,processing devices, processing entities, set-top boxes, relays, routers,network access points, base stations, the like, and/or any combinationof devices or entities adapted to perform the functions, operations,and/or processes described herein. As shown in FIG. 45, the usercomputing entity 804 can include communication components/elements, suchas an antenna 912, a transmitter 914 (e.g., radio), and a receiver 916(e.g., radio). Similarly, the user computing entity 804 can include aprocessing element/component 918 (e.g., CPLDs, microprocessors,multi-core processors, cloud processors, coprocessing entities, ASIPs,microcontrollers, and/or controllers) that provides signals to andreceives signals from communication elements/components.

The signals provided to and received from the transmitter 914 and thereceiver 916, respectively, may include signaling information/data inaccordance with air interface standards of applicable wireless systems.In this regard, the user computing entity 804 may be capable ofoperating with one or more air interface standards, communicationprotocols, modulation types, and access types. More particularly, theuser computing entity 804 may operate in accordance with any of a numberof wireless communication standards and protocols, such as thosedescribed above with regard to the central computing entity 802. In aparticular embodiment, the user computing entity 804 may operate inaccordance with multiple wireless communication standards and protocols,such as UMTS, CDMA2000, 1×RTT, WCDMA, GSM, EDGE, TD-SCDMA, LTE, E-UTRAN,EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR, NFC, Bluetooth,USB, and/or the like. Similarly, the user computing entity 804 mayoperate in accordance with multiple wired communication standards andprotocols, such as those described above with regard to the centralcomputing entity 802 via a network interface 908.

Via these communication standards and protocols, the user computingentity 804 can communicate with various other entities using conceptssuch as Unstructured Supplementary Service Data (USSD), Short MessageService (SMS), Multimedia Messaging Service (MMS), Dual-ToneMulti-Frequency Signaling (DTMF), and/or Subscriber Identity ModuleDialer (SIM dialer). The user computing entity 804 can also downloadchanges, add-ons, and updates, for instance, to its firmware, software(e.g., including executable instructions, applications, programmodules), and operating system.

According to one embodiment, the user computing entity 804 may includelocation determining elements/components, aspects, devices, modules,functionalities, and/or similar words used herein interchangeably. Forexample, the user computing entity 804 may include outdoor positioningaspects, such as a location module adapted to acquire, for example,latitude, longitude, altitude, geocode, course, direction, heading,speed, universal time (UTC), date, and/or various otherinformation/data. In one embodiment, the location module can acquireinformation/data, sometimes known as ephemeris information/data, byidentifying the number of satellites in view and the relative positionsof those satellites (e.g., using global positioning systems (GPS)). Thesatellites may be a variety of different satellites, including Low EarthOrbit (LEO) satellite systems, Department of Defense (DOD) satellitesystems, the European Union Galileo positioning systems, the ChineseCompass navigation systems, Global Navigation Satellite System(GLONASS), Indian Regional Navigational satellite systems, and/or thelike. This information/data can be collected using a variety ofcoordinate systems, such as the Decimal Degrees (DD); Degrees, Minutes,Seconds (DMS); Universal Transverse Mercator (UTM); Universal PolarStereographic (UPS) coordinate systems; and/or the like. Alternatively,the location information/data can be determined by triangulating theuser computing entity's 804 position in connection with a variety ofother systems, including cellular towers, Wi-Fi access points, and/orthe like. Similarly, the user computing entity 804 may include indoorpositioning aspects, such as a location module adapted to acquire, forexample, latitude, longitude, altitude, geocode, course, direction,heading, speed, time, date, and/or various other information/data. Someof the indoor systems may use various position or location technologiesincluding RFID tags, indoor beacons or transmitters, Wi-Fi accesspoints, cellular towers, nearby computing devices (e.g., smartphones,laptops) and/or the like. For instance, such technologies may includethe iBeacons, Gimbal proximity beacons, Bluetooth Low Energy (BLE)transmitters, Bluetooth Smart, NFC transmitters, and/or the like. Theseindoor positioning aspects can be used in a variety of settings todetermine the location of someone or something to within inches orcentimeters.

The user computing entity 804 may also comprise a user interface (thatcan include a display 919 coupled to a processing element/component 918)and/or a user input interface (coupled to a processing element/component918). For example, the user interface may be a user application,browser, user interface, interface, and/or similar words used hereininterchangeably executing on and/or accessible via the user computingentity 804 to interact with and/or cause display of information/datafrom the central computing entity 802, as described herein. The userinput interface can comprise any of a number of devices or interfacesallowing the user computing entity 804 to receive information/data, suchas a keypad 920 (hard or soft), a touch display, voice/speech or motioninterfaces, or other input device. In embodiments including a keypad920, the keypad 920 can include (or cause display of) the conventionalnumeric (0-9) and related keys (#, *), and other keys used for operatingthe user computing entity 804 and may include a full set of alphabetickeys or set of keys that may be activated to provide a full set ofalphanumeric keys. In addition to providing input, the user inputinterface can be used, for example, to activate or deactivate certainfunctions, such as screen savers and/or sleep modes.

The user computing entity 804 can also include memoryelements/components—such as volatile storage or memory 922 and/ornon-volatile storage or memory 924, which can be embedded and/or may beremovable. For example, the non-volatile memory may be ROM, PROM, EPROM,EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks, CBRAM, PRAM,FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipede memory, racetrackmemory, and/or the like. The volatile memory may be RAM, DRAM, SRAM, FPMDRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM,T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory,and/or the like. The volatile and non-volatile storage or memory canstore databases, database instances, database management systems,information/data, applications, programs, program modules, scripts,source code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, and/or the like to implement thefunctions of the user computing entity 804. As indicated, this mayinclude a user application that is resident on the entity or accessiblethrough a browser or other user interface for communicating with thecentral computing entity 802, mobile carrier computing entity 806, UAVcomputing entity 808, delivery vehicle computing entity 810, and/orvarious other computing entities.

In another embodiment, the user computing entity 804 may include one ormore elements/components or functionality that are the same or similarto those of the central computing entity 802, as described in greaterdetail above. As will be recognized, these architectures anddescriptions are provided for exemplary purposes only and are notlimiting to the various embodiments.

C. Exemplary UAV Computing Entity

FIG. 49 provides an illustrative schematic representative of the UAVcomputing entity 808 that can be used in conjunction with embodiments ofthe present invention. As described above, the elements/components ofthe UAV computing entity 808 may be similar to those described withregard to the central computing entity 802, the user computing entity804, and/or the mobile carrier computing entity 806. In one embodiment,the UAV computing entity 808 may also include and/or be associated withone or more control elements/components (not shown) for controlling andoperating the UAV 100 as described herein. As shown in FIG. 49, the UAVcomputing entity 808 can include communication elements/components 908,such as those described above with regard to the central computingentity 802 and/or the user computing entity 804. For example, the UAVcomputing entity 808 may operate in accordance with any of a number ofwireless communication standards, such as UMTS, CDMA2000, 1×RTT, WCDMA,GSM, EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-FiDirect, WiMAX, UWB, IR, NFC, Bluetooth, BLE, Wibree, USB, and/or thelike. Similarly, the UAV computing entity 808 may operate in accordancewith multiple wired communication standards and protocols, such as thosedescribed with regard to the central computing entity 802, the usercomputing entity 804, and/or the like via the communicationelements/components. Thus, the UAV 100 (e.g., the UAV computing entity808) may be able to communicate with various computingentities—including user computing entities 804 (e.g., smart home entity)to, for example, provide an instruction to open a garage door, provide anotification/message and/or the like. The UAV computing entity 808 mayalso include one or more processing elements/components 405, includingthose described with regard to the central computing entity 802 and/orthe user computing entity 804.

As indicated, a UAV 100 (e.g., the UAV computing entity 808) may havethe ability to operate in accordance with multiple long-range andshort-range communication standards and protocols and use multiplewireless carriers (e.g., China Mobile, Vodafone, Telefonica, T-Mobile,Verizon, AT&T, and Qtel). For example, in a single geographic area(e.g., country, region, state, county, city, or town), there may bemultiple wireless carriers providing wireless services. Similarly, incommunicating with a primary parcel delivery vehicle 10 (or variousother computing entities), a UAV computing entity 808 may have theability to use long-range and short-range communication standards andprotocols depending the UAV's 100 proximity to the primary parceldelivery vehicle 10 and/or the UAV's 100 operational state (e.g., if thepropulsion members 102 active or inactive).

In one embodiment, a central computing entity 802 can manage the accessof the UAV computing entity 808 to the plurality of wireless carriers inone or more geographic areas and/or use of the long-range andshort-range communication standards and protocols. For example, a UAV100 associated with the various geographic areas can be activated withthe various wireless carriers. Activating a UAV computing entity 808with wireless carriers may include registering each UAV computing entity808 with the wireless carriers from which services are desired (e.g.,based on the UAV's 100 operating area). With numerous UAV 100 to manage,the central computing entity 802 may provide for an automated activationprocess. In certain embodiments, it may not be practical for a UAV 100in a given geographic area to be configured to operate with more than afew wireless carriers. For instance, in one embodiment, it may besufficient for the UAV 100 to be activated on two wireless carriers: aprimary wireless carrier and a secondary wireless carrier. In otherembodiments, a third or fourth activation may be justified based on theavailable wireless services and actual coverage patterns in thegeographic area in which a UAV 100 will be used.

In addition to activating the UAV computing entity 808, the centralcomputing entity 802 may be used to configure the UAV computing entity808 to use the wireless services of wireless carriers and/or the variouslong-range and short-range communication standards and protocols. To doso, the central computing entity 802 may create and provide aconfiguration (e.g., a configuration file) for all UAVs 100 operatingwithin a specific geographic area, such as a country, region, state,county, city, town, or other area. The configuration may also provide anorder in which the wireless carriers should be accessed and/or thestates or proximity to a primary parcel delivery vehicle 10 in which thelong-range and short-range communication standards and protocols shouldbe used.

In one embodiment, the central computing entity 802 may create andprovide a UAV-type configuration for each type of UAV computing entity808 used by an enterprise. For example, an enterprise may have differenttypes of UAV computing entities 808, each using different hardware,firmware, and software. Thus, the different configurations may be ratherextensive and be customized down to, for example, the individual UAVcomputing entity 808. In one embodiment, UAV-type configurations may beused to provide the UAV computing entity 808 with, for instance, tuningparameters with build-time embedded default values, such as the numberof occurrences of a failed carrier dial-up would be permitted beforechanging the current wireless carrier (e.g., changing from a primarywireless carrier to a secondary wireless carrier).

As indicated, the configurations may identify a primary wireless carrierand one or more secondary wireless carriers to use for wirelessservices. In one embodiment, the primary wireless carrier may be thewireless carrier the UAV computing entity 808 should use under normalconditions. The one or more secondary wireless carriers may be thewireless carriers the UAV computing entity 808 can use in the event ofcommunication issues, for example, with the primary wireless carrier.For instance, the UAV computing entity 808 may switch from the primarywireless carrier to a secondary wireless when, for instance, somethingfails and is not recoverable by establishing a new session with theprimary wireless carrier. Identifying the appropriate secondary wirelesscarrier to be used may be based on a variety of factors, includinglocation, coverage availability, signal strength, and/or the like.

Similarly, the configurations may identify a primary long-rangestandard/protocol and a secondary short-range standard/protocol. In oneembodiment, the primary long-range standard/protocol (e.g., LTE, GSM)may be the wireless standard/protocol the UAV computing entity 808should use when its operational state is on or active (e.g., when thepropulsion members 102 of the UAV 100 are active). The secondaryshort-range standard/protocol (e.g., BLE, UWB) may be the wirelessstandard/protocol the UAV 100 should use when its operational state isoff or inactive (e.g., its propulsion members 102 inactive). Using thesecondary wireless standard/protocol may also be determined based on theUAV's 100 proximity to the primary parcel delivery vehicle 10. Forinstance, when the UAV 100 is within 100 feet of the primary parceldelivery vehicle 10, the UAV may use a short-range standard/protocol ora dual-band approach until its operational state changes.

In one embodiment, by using multiple technologies and a common controlmechanism (e.g., software), the UAV computing entity 808 can managecommunications with multiple wireless carriers, using variousstandards/protocols, and drive the network connections. This may includepath switching (e.g., software path switching) accomplished atbuild-time where different hardware is to be used and/or at run-timewhere it makes sense to act in different ways over time based on theactual conditions identified. Generally, path switching may refer tobranching of software, for example, to address the needs of a specificUAV computing entity 808. Moreover, to adapt to different UAV computingentities 808, conditional compile-time switches can be used to enableblocks of code suitable for a specific UAV computing entity 808.

According to one embodiment, the UAV computing entity 808 may includelocation determining elements/components, aspects, devices, modules,functionalities, and/or similar words used herein interchangeably. Aspreviously describe, such outdoor positioning aspects may include alocation module adapted to acquire, for example, latitude, longitude,altitude, geocode, course, direction, heading, speed, UTC, date, and/orvarious other information/data. In one embodiment, the location modulecan acquire information/data, sometimes known as ephemerisinformation/data, by identifying the number of satellites in view andthe relative positions of those satellites (e.g., GPS). The satellitesmay be a variety of different satellites, including LEO satellitesystems, GLONASS satellite systems, DOD satellite systems, the EuropeanUnion Galileo positioning systems, the Chinese Compass navigationsystems, Indian Regional Navigational satellite systems, and/or thelike. This information/data can be collected using a variety ofcoordinate systems, such as the DD; DMS; UTM; UPS coordinate systems;and/or the like. Alternatively, the location information/data can bedetermined by triangulating the user computing entity's 804 position inconnection with a variety of other systems, including cellular towers,Wi-Fi access points, and/or the like. Similarly, the UAV computingentity 808 may include indoor positioning aspects, such as a locationmodule adapted to acquire, for example, latitude, longitude, altitude,geocode, course, direction, heading, speed, time, date, and/or variousother information/data. Some of the indoor systems may use variousposition or location technologies including RFID tags, indoor beacons ortransmitters, Wi-Fi access points, cellular towers, nearby computingdevices (e.g., smartphones, laptops) and/or the like. For instance, suchtechnologies may include the iBeacons, Gimbal proximity beacons, BLEtransmitters, Bluetooth Smart, NFC transmitters, and/or the like. Theseindoor positioning aspects can be used in a variety of settings todetermine the location of someone or something to within inches orcentimeters.

The UAV computing entity 808 can also include one or memoryelements/components 915, which can be embedded and/or may be removable.For example, the non-volatile memory may be ROM, PROM, EPROM, EEPROM,flash memory, MMCs, SD memory cards, Memory Sticks, CBRAM, PRAM, FeRAM,NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipede memory, racetrack memory,and/or the like. The volatile memory may be RAM, DRAM, SRAM, FPM DRAM,EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM,Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory, and/or thelike. The volatile and non-volatile storage or memory can storedatabases, database instances, database management systems,information/data, applications, programs, program modules, scripts,source code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, and/or the like to implement thefunctions of the UAV computing entity 808.

As indicated, the UAV computing entity 808 may include and/or beassociated with one or more sensing elements/components, modules, and/orsimilar words used herein interchangeably. In embodiments, the one ormore sensing elements/components include the ground landing sensors 162,the vehicle landing sensors 164, the route/flight guidance sensors 166,and the cameras 168. The UAV computing entity 808 may include sensingelements/components, such as motor/engine, fuel, battery, speed,route/flight time, altitude, barometer, air telemetry, ground telemetry,gyroscope, pressure, location, weight, emissions, temperature, magnetic,current, tilt, motor/engine intake, motor/engine output, and/or carriersensors. The sensed information/data may include, but is not limited to,air speed information/data, ground speed information/data, emissionsinformation/data, RPM information/data, acceleration information/data,tilt information/data, oil pressure information/data, pressureinformation/data, rotational information/data, distanceinformation/data, fuel information/data, idle information/data, weightinformation/data, and/or the like (which may be referred to astelematics information/data). The sensing elements/components mayinclude environmental sensors, such as air quality, chemical,precipitation, temperature sensors, and/or the like. Thus, the sensedinformation/data may also include carbon monoxide (CO), nitrogen oxides(NOx), sulfur oxides (SOx), Ethylene Oxide (EtO), ozone (O3), hydrogensulfide (H2S) and/or ammonium (NH4) information/data, temperatureinformation/data, pressure information/data, and/or meteorologicalinformation/data (which may be referred to as weather or atmosphericinformation/data).

As described above, the ground landing sensors 162 and the vehiclelanding sensors 164 may include one or more sonar sensors, light sensors(e.g., LIDAR, LiDAR, and LADAR), magnetic-field sensors, radio wavesensors (e.g., RADAR), thermals sensors, infrared sensors, imagesensors, and/or the like. Further, the vehicle landing sensors 164 andthe cameras 168 may include one or more image sensors for capturing,collecting, and/or recording image information/data (e.g., sensedinformation/data). The image information/data can be captured and storedin a variety of formats. For example, the image information/data(including 360° video) can be captured in or converted to a variety offormats, such as Joint Photographic Experts Group (JPEG), Motion JPEG(MJPEG), Moving Picture Experts Group (MPEG), Graphics InterchangeFormat (GIF), Portable Network Graphics (PNG), Tagged Image File Format(TIFF), bitmap (BMP), H.264, H.263, Flash Video (FLV), Hypertext MarkupLanguage 5 (HTML5), VP6, VP8, 4K, and/or the like. Such sensedinformation/data can be captured, collected, and/or or recorded using avariety of techniques and approaches for various purposes (e.g.,takeoff, landing, delivery, collision avoidance, routing, and/or thelike).

D. Exemplary Delivery Vehicle Computing Entity

Referring again to FIG. 46, the one or more delivery vehicle computingentities 810 may be attached, affixed, disposed upon, integrated into,or part of a primary parcel delivery vehicle 10. The delivery vehiclecomputing entity 810 may collect telematics information/data (includinglocation information/data) and transmit/send the information/data tovarious other computing entities via one of several communicationmethods.

In one embodiment, the delivery vehicle computing entity 810 mayinclude, be associated with, or be in wired or wireless communicationwith one or more processing elements/components, location determiningelements/components, one or more communication elements/components, oneor more sensing elements/components, one or more memory locationdetermining elements/components, one or more power sources, and/or thelike. Such elements/components may be similar to those described withregard to the central computing entity 802, the user computing entity804, the mobile carrier computing entity 806, and/or the UAV computingentity 808.

In one embodiment, the one or more location determiningelements/components may be one of several components in wired orwireless communication with or available to the delivery vehiclecomputing entity 810. Moreover, the one or more location determiningelements/components may be compatible with various satellite ornavigation systems, coordinate systems, and/or the like. Thus, the oneor more location determining elements/components may be used to receivelatitude, longitude, altitude, heading or direction, geocode, course,position, time, and/or speed information/data (e.g., referred to hereinas telematics information/data and further described herein below). Theone or more location determining elements/components may alsocommunicate with the central computing entity 802, the delivery vehiclecomputing entity 810, mobile carrier computing entity 806, and/orsimilar computing entities.

As indicated, in addition to the one or more elements/components, thedelivery vehicle computing entity 810 may include and/or be associatedwith one or more sensing elements/components, modules, and/or similarwords used herein interchangeably. For example, the sensingelements/components may include vehicle sensors, such as motor/engine,fuel, odometer, hubometer, tire pressure, location, weight, emissions,door, and speed sensors. The sensed information/data may include, but isnot limited to, speed information/data, emissions information/data, RPMinformation/data, tire pressure information/data, oil pressureinformation/data, seat belt usage information/data, distanceinformation/data, fuel information/data, idle information/data, and/orthe like (which may be referred to as telematics information/data). Thesensing elements/components may include environmental sensors, such asair quality sensors, temperature sensors, and/or the like. Thus, thesensed information/data may also include CO, NOx, SOx, EtO, O3, H2S,and/or NH4 information/data, and/or meteorological information/data(which may be referred to as weather, environmental, and/or atmosphericinformation/data).

In one embodiment, the delivery vehicle computing entity 810 may furtherbe in communication with a vehicle control module or system. The vehiclecontrol module or system, which may be a scalable and subservient deviceto the delivery vehicle computing entity 810, may have information/dataprocessing capability to decode and store analog and digital inputs fromvehicle systems and sensors. The vehicle control module or system mayfurther have information/data processing capability to collect andpresent telematics information/data to the J-Bus (which may allowtransmission to the delivery vehicle computing entity 810), and outputstandard vehicle diagnostic codes when received from a vehicle'sJ-Bus-compatible onboard controllers and/or sensors.

As will be recognized, the delivery vehicle computing entity 810 caninclude communication elements/components, such as those described withregard to the central computing entity 802, UAV computing entity 808,and/or user computing entity 804. Furthermore the delivery vehiclecomputing entity 810 may be communicatively coupled to the robotprocessor 522 and the conveyor controller 460 and may control operationof the robot 500 and the conveyor 440, as will be described in greaterdetail herein.

E. Exemplary Parcel Carrier Computing Entity

In one embodiment, a parcel carrier computing entity 212 may include oneor more elements/components that are functionally similar to those ofthe central computing entity 802, user computing entity 804, UAVcomputing entity 808, and/or delivery vehicle computing entity 810. Forexample, in one embodiment, each parcel carrier computing entity 212 mayinclude one or more processing elements/components (e.g., CPLDs,microprocessors, multi-core processors, cloud processors, coprocessingentities, ASIPs, microcontrollers, and/or controllers), one or moredisplay device/input devices (e.g., including user interfaces), volatileand non-volatile storage or memory elements/components, and/or one ormore communications elements/components. For example, the user interfacemay be a user application, browser, user interface, interface, and/orsimilar words used herein interchangeably executing on and/or accessiblevia the parcel carrier computing entity 212 to interact with and/orcause display of information/data from the central computing entity 802,as described herein. This may also enable the parcel carrier computingentity 212 to communicate with various other computing entities, such asthe UAV computing entity 808, and/or various other computing entities.As will be recognized, these architectures and descriptions are providedfor exemplary purposes only and are not limiting to the variousembodiments.

F. Exemplary Mobile Carrier Computing Entity

In one embodiment, a mobile carrier computing entity 806 may include oneor more elements/components that are functionally similar to those ofthe central computing entity 802, user computing entity 804, UAVcomputing entity 808, and/or delivery vehicle computing entity 810. Forexample, in one embodiment, each mobile carrier computing entity 806 mayinclude one or more processing elements/components (e.g., CPLDs,microprocessors, multi-core processors, cloud processors, coprocessingentities, ASIPs, microcontrollers, and/or controllers), one or moredisplay device/input devices (e.g., including user interfaces), volatileand non-volatile storage or memory elements/components, and/or one ormore communications elements/components. For example, the user interfacemay be a user application, browser, user interface, interface, and/orsimilar words used herein interchangeably executing on and/or accessiblevia the mobile carrier computing entity 806 to interact with and/orcause display of information/data from the central computing entity 802,as described herein. This may also enable the mobile carrier computingentity 806 to communicate with various other computing entities, such asuser computing entities 804, and/or various other computing entities. Aswill be recognized, these architectures and descriptions are providedfor exemplary purposes only and are not limiting to the variousembodiments.

Reference will now be made to delivery methods for delivering parcels300 via the UAVs 100. In various embodiments, the UAVs 100 may bedispatched based on logical groupings, geofencing, and the like.

G. Geographic Information/Data Database

In one embodiment, each computing entity may include or be incommunication with one or more geographic information/data database (notshown) configured to access, process, provide, manipulate, store, and/orthe like map information/data. For example, the geographicinformation/data database may include or have access to a mapinformation/data database that includes a variety of data (e.g., mapinformation/data) utilized for displaying a map, constructing aroute/flight or navigation path, and/or other map related functions forterrestrial, nautical, and/or aerial vehicles. For example, thegeographic information/data database may communicate with or comprise ageographic information/data database comprising map information/dataprovided by a map provider computing entity. For example, a geographicinformation/data database may include node data, waypoint records,street/flight/route segment records, point of interest (POI) datarecords, event of interest data records, serviceable point 5901 datarecords, and other data records. In one embodiment, the other datarecords include cartographic (“carto”) data records, routing datarecords (e.g., for routing and navigating vehicles to particularpoints), and/or the like. For example, the geographic information/datadatabase may comprise map information/data including boundary, location,and attribute information/data corresponding to the various serviceablepoints 5901, POIs, events of interest, and/or the like.

One or more portions, components, areas, layers, features, text, and/orsymbols of the POI or event data can be stored in, linked to, and/orassociated with one or more of these data records. For example, one ormore portions of the POI, event data, or recorded route/flightinformation can be matched with respective map or geographic records viaposition or GNSS and/or GPS) data associations (such as using known orfuture map matching, geo-coding, and/or reverse geo-coding techniques),for example. As will be recognized, the map information/data can bestored using a variety of formats, layers, and/or the like—includingshapefiles, ArcMaps, geodatabases, coverages, imagery, rasters,computer-aided drafting (CAD) files, other storage formats, and/or thelike. For instance, the geographic information/data database canappropriately store/record map information/data as a part of a digitalmap, e.g., as part of a feature layer, raster layer, service layer,geoprocessing layer, basemap layer, service are layer, constituent arealayer, and/or the like.

In an example embodiment, the street/flight/route segment data recordsare segments representing roads, streets, flight paths, paths, and/orthe like. The node data records are end points corresponding to therespective links or segments of the street/flight/route segment datarecords. The street/flight/route segment data records and the node datarecords represent a road networks or flight paths, used by various typesof vehicles. Alternatively, the geographic information/data database cancontain path segments and node data records or other data that representpedestrian paths or areas in addition to or instead of thestreet/flight/route segment data records, for example. The object ordata structure of the street/flight/route segments and other records maycomprise a variety of information/data associated with each map element.In some examples, this information/data may include a consignee name,pick-up or delivery identifier, primary delivery point (e.g., firstdesired delivery point/location 5902), secondary delivery point, streetname, street number, street prefix, street suffix, street type, city,state, province, territory, country, postal code, residential orcommercial indicator, street classification, directionals (e.g., one way<specific to which way> or both ways), longitude and latitude, geocode,location identifier, and/or the like. For example, in one embodiment, amap element may be represented by and/or associated with a longitude andlatitude, a geocode, a nearest street/flight/route segment, an address,and/or the like. Similarly, street/flight/route segments may berepresented by or associated with a name, a segment identifier, aconnecting node, an address or address range, a series of longitude andlatitude coordinates, and/or the like that define the overall shape andlocation of the street/flight/route segment. As will be recognized, avariety of other approaches and techniques can be used to adapt tovarious needs and circumstances.

The street/flight/route segments and nodes can be associated withattributes, such as geographic coordinates (e.g., latitude andlongitude), names or identifiers, street names, address ranges, speedlimits, turn restrictions at intersections, and other navigation relatedattributes, as well as serviceable points, events of interest, and/orPOIs, such as gasoline stations, hotels, restaurants, museums, stadiums,offices, waypoints, automobile dealerships, auto repair shops,buildings, stores, parks, etc. For example, serviceable points 5901,events of interest, and/or POIs can be represented in digital maps asbeing accessible by one or more street networks or street segments of astreet network. Serviceable points 5901, events of interest, POIs,street networks, and/or the like can be represented in digital maps asnavigable/traversable/travelable segments or points for traveling toand/or from serviceable points 5901, waypoints, events of interest,and/or POIs.

The geographic information/data database can include data about theserviceable points 5901, events of interest, and/or POIs and theirrespective locations in the serviceable points 5901, events of interest,and/or POI data records. The geographic information/data database canalso include data about places, such as cities, towns, or othercommunities, and other geographic features, such as bodies of water,mountain ranges, etc. Such place or feature data can be part of the POIdata or can be associated with POIs or POI data records (such as a datapoint used for displaying or representing a position of a city). Inaddition, the geographic information/data database can include and/or beassociated with event information/data (e.g., traffic incidents,constructions, scheduled events, unscheduled events, etc.) associatedwith the POI data records or other records of the geographicinformation/data database. For example, in one embodiment, a serviceablepoint 5901, event of interest, and/or POI may be represented by and/orassociated with a longitude and latitude, a geocode, a neareststreet/flight/route segment, an address, and/or the like. As will berecognized, a variety of other approaches and techniques can be used toadapt to various needs and circumstances.

In one embodiment, the geographic information/data database may storedigital maps. In another embodiment, the geographic information/datadatabase may be in communication with or associated with one or more mapor content provider computing entities (e.g., mappingwebsites/servers/providers/databases, including providers such asmaps.google.com, bing.com/maps, mapquest.com, Tele Atlas®, NAVTEQ®,and/or the like) that provide map information/data (or other content) ofdigital maps to a variety of users and/or entities. Using the digitalmaps, an appropriate computing entity can provide map information/data,for example, about serviceable points 5901, events of interest, and/orPOIs (e.g., their locations, attributes, and/or the like) and/or theircorresponding street networks based on map information/data.

The geographic information/data database can be maintained by the map orcontent provider (e.g., a map developer) in association with theservices platform. By way of example, the map developer can collectgeographic data to generate and enhance the geographic information/datadatabase. There can be different ways used by the map developer tocollect data. These ways can include obtaining data from other sources,such as municipalities or respective geographic authorities. Thegeographic information/data database can be a master geographicinformation/data database stored in a format that facilitates updating,maintenance, and development. For example, the master geographicinformation/data database or data in the master geographicinformation/data database can be in an Oracle spatial format, .kml, SQL,PostGIS, or other spatial format, such as for development or productionpurposes. The Oracle spatial format or development/production databasecan be compiled into a delivery format, such as a geographic data files(GDF) format. The data in the production and/or delivery formats can becompiled or further compiled to form geographic information/datadatabase products or databases, which can be used in end user computingentities or systems.

5. Additional Features, Functionality, and Operations

A. Parcel Information/Data

In one embodiment, the process may begin by the central computing entity802 generating and/or receiving parcel information/data for one or moreparcels 300. For example, a user may initiate the transportation processby entering identifying information/data into the central computingentity 802. In various embodiments, the user (e.g., a user or userrepresentative operating a user computing entity 804) may access awebpage, application, dashboard, browser, or portal of a carrier. Afterthe user is identified (e.g., based on his or her profile), the user mayinitiate a parcel 300. In various embodiments, the central computingentity 802 may then provide or be in communication with a user interface(e.g., browser, dashboard, application) for the user to provide parcelinformation/data which includes certain details regarding the parcel300. In various embodiments, the parcel information/data may include aname, street address, city, state, postal code, country, telephonenumber, and/or the like for both the consignor and the consignee. Invarious embodiments, the user interface may comprise a fillable formwith fields including ship-from information/data and ship-toinformation/data. In various embodiments, some of the information/datafields may be pre-populated. For example, if the user logged into aregistered account/profile, the address information/data entered duringregistration may be pre-populated in certain information/data fields. Insome embodiments, the user may also have a digital address bookassociated with the account comprising address information/data forpossible ship-to and/or ship-from information/data. The user may be ableto select certain ship-to and/or ship-from information/data from theaddress book for the associated parcel 300.

In one embodiment, after the central computing entity 802 receives theship-to and/or ship-from information/data from the user, the centralcomputing entity 802 may perform one or more validation operations. Forexample, the central computing entity 802 may determine whether theprimary address (and/or other addresses) in the specified country orpostal code is eligible for a pick-up or delivery. The central computingentity 802 may also determine whether the primary address (and/or othersecondary addresses) is valid, e.g., by passing the primary addressthrough one or more address cleansing or standardization systems. Thecentral computing entity 802 may perform a variety of fraud preventionmeasures as well, such as determining whether the users (or one of thedelivery addresses) have been “blacklisted” from user pick-up and/ordelivery. As will be recognized, a variety of other approaches andtechniques can be used to adapt to various needs and circumstances.

In addition to ship-to and/or ship-from information/data, the parcelinformation/data may also include service level information/data. Theservice level options may be, for example, Same Day UAV, Same DayGround, Next Day UAV, Next Day Ground, Overnight, Express, Next Day AirEarly AM, Next Day Air Saver, Jetline, Sprintline, Secureline, 2nd DayAir, Priority, 2nd Day Air Early AM, 3 Day Select, Ground, Standard,First Class, Media Mail, SurePost, Freight, and/or the like.

In one embodiment, the central computing entity 802 (a) may be providedparcel 300 characteristics and attributes in the parcel information/dataand/or (b) may determine parcel 300 characteristics and attributes fromthe parcel information/data. The characteristics and attributes mayinclude the dimensions, weight, transportation classifications, plannedmovements in the carrier's transportation and logistics network, plannedtimes, and/or the like for various parcels 300. For example, the length,width, height, base, radius, and weight can be received as inputinformation/data and/or can be determined or collected by variouscarrier systems. For example, sensors or cameras may be positioned tocapture or determine the length, width, height, and weight (includingdimensional weight) of a parcel 300 as it moves along the conveyor,moves in or out of loading bay, is carried by a lift truck, istransported through the carrier's transportation and logistics network,and/or the like.

In one embodiment, with such information/data, the central computingentity 802 can determine/identify the cube/volume for each parcel 300.The units of measurement for the equations may be established so thatthe size produced by the determinations is in cubic feet, or cubicinches, or any other volumetric measure. In one embodiment, afterdetermining the cube/volume for a parcel 300 (and/or making variousother determinations), the central computing entity 802 can apply aclassification to the parcel 300 based at least in part on thecube/volume. The classifications may include (1) size category oneparcels 300, (2) size category two parcels 300, (3) size category threeparcels 300, and/or (4) size category four parcels 300. By way ofexample, (1) size category one parcels 300 may be defined as beingwithin >0 and ≤2 cubic feet, (2) size category two parcels 300 may bedefined as being within >2 and ≤4 cubic feet, (3) size category threeparcels 300 may be defined as being within >4 and ≤6 cubic feet, and/or(4) size category four parcels 300 may be defined as being over >6 cubicfeet. As will be recognized, a variety of other approaches andtechniques can be used to adapt to various needs and circumstances. Thiscan facilitate determining the types of delivery options that areavailable for a parcel, such as UAV delivery or primary parcel 300delivery vehicle delivery 10.

In one embodiment, the central computing entity 802 may assign orassociate one or more planned times for each parcel 300—along with aplanned time for specific activities for the parcel 300, each stop of aroute/flight, each route/flight, and/or the like. A planned time may bethe time for handling (e.g., sorting, re-wrapping, loading, unloading,inspecting, picking up, delivering, labeling, over-labeling, engaging,disengaging, and/or the like) a parcel 300. In one embodiment, eachparcel 300, each activity, each stop of a route/flight, eachroute/flight, and/or the like may have or be associated with totalplanned times and/or additive planned times. The planned times may bebased on historical information/data, such as average planned times.

As indicated, a planned time may comprise a total planned time for aparcel 300, an activity, a stop of a route/flight, a route/flight,and/or the like. The total planned time may comprise various additiveplanned times (both of which are referred to herein interchangeably asplanned times). The planned times may be based on a variety of factorsor parameters. For example, the planned time may be based on thecube/volume and/or weight of the parcel 300—e.g., it may take more timeto move a parcel 300 that weighs 11.52 pounds from a conveyor belt thanto move a parcel 300 that weighs 0.32 pounds from the same conveyorbelt. Further, the planned time factors and/or parameters may alsocontemplate or include the type of parcel 300, such as whether theparcel 300 requires special handling. The planned time factors and/orparameters may also contemplate the service level of and/or activitiesto be carried out for the parcel 300. Based on the factors andparameters, for instance, the central computing entity 802 may store,have access to, and/or may forecast/estimate planned times for sorting,handling, conveying, scanning, picking up, delivering, and/or the likevarious parcels 300. For purposes of illustration and not of limitation,for sorting a parcel 300 from a belt conveyor to a position in a fulllength trailer, (1) a size category one parcel may be assigned orassociated with a 1 second additive planned time, (2) a size categorytwo parcel assigned a 1.5 second additive planned time, and so forth.Similarly, for a load operation from a warehouse to a vehicle, forinstance, (1) each size category one parcel may be assigned orassociated with 5 seconds of planned time, (2) each size category twoparcel may be assigned or associated with 7 seconds of planned time, (3)each size category three parcel may be assigned or associated with 10seconds of planned time, and (4) each size category four parcel may beassigned or associated with 20 seconds of planned time. Moreover, (1)each special handling category one parcel may be assigned or associatedwith 25 seconds of additive planned time, (2) each special handlingcategory two parcel may be assigned or associated with 45 seconds ofadditive planned time, and (3) each special handling category threeparcel may be assigned or associated with 33 seconds of additive plannedtime. The additive planned times may also be specific to carrierequipment: unload systems, load systems, sortation systems, vehicles,re-wrap systems, weighing systems, inspection systems, tools, and/or anyother suitable systems. Thus, the additive planned times may vary fordifferent types of systems (e.g., unload conveyor A, unload conveyor B)since the times for handling specific tasks associated with thedifferent systems may vary. Additionally, some of the additive plannedtimes may vary based on different types of vehicles since a storage areaof the vehicles may vary based on the size of the vehicles. Forinstance, it may take longer or shorter times to walk to or accesslocations of the storage area and access walls, shelves, and/or the likeof the storage area. In this example, the central computing entity 802may determine/identify additive planned times associated with setup ofconveyors (e.g., an unload conveyor). Further, there may be an additiveplanned time for loading the parcel 300 onto a primary parcel 300vehicle 10 or conveyor, sorting the parcel 300 at a hub or other center,re-wrapping and over-labeling the parcel 300, scanning and walking theparcel 300 from a primary parcel 300 vehicle 10 to its final deliverydestination, and/or the like.

The additive planned times may also be specific to vehicles (which alsomay be referred to herein as equipment) used in load, unload, pick-up,and/or delivery operations of parcels 300, as well as one or morebundles/containers. For instance, the central computing entity 802 maydetermine the number of parcels 300 that may be loaded on or unloadedfrom the trailer or truck within a given time period based on the sizesof trucks/trailers (e.g., 40 foot trailers, 50 foot trailers) and/or thelike. As such, in response to identifying a selected primary parcel 300vehicle 10 from which to unload and/or load parcels 300, the centralcomputing entity 802 may determine/identify additive planned times(e.g., an unload system, a load system) based in part on the size of thetrailer/truck and/or equipment being used. As will be recognized, longerlength trailers/trucks may require greater additive planned timesrelative to shorter length trailers, for example, to walk off parcels300 (e.g., parcels 300), and may, but need not, require longerconveyors, which may require more setup time than shorter conveyors.Additionally, in some embodiments, various size category one parcels 300may be stored in one or more bundles/containers (e.g., bags, tote boxes,and/or the like). As such, in an instance in which the central computingentity 802 may determine that a bundle/container includes size categoryone parcels 300, the central computing entity 802 may assign an additiveplanned time to the bundle/container which may decrease or increase thehandling time for size category one parcels 300 for a given load.

In one embodiment, the central computing entity 802 candetermine/identify a total planned time for handling, transporting,warehousing, sorting, loading, unloading, re-wrapping, inspecting,picking up, delivering, and/or the like a parcel 300 from ingestion intothe carrier's transportation and logistics network through to deliveryat its final delivery destination. Additionally, the central computingentity 802 can determine planned times for different legs or activitiesfor a given parcel 300 (e.g., a planned time for pick-up or delivery ofa parcel 300). In one embodiment, the total planned time may be anestimated time irrespective of the various potential additive plannedtimes.

Continuing with the above example, for the size category four parcelwith a cube of 2.315 cubic feet weighing 15 pounds, the centralcomputing entity 802 may assign a total planned time for picking up aparcel 300 from Corporation ABC's Distribution warehouse in Orlando,Fla., and delivering the same to 123 Springfield Road, Norcross, Ga.30092. The total planned time may be estimated based on historicalinformation/data for similar parcels 300 and/or be the sum of variousactivities to be carried out for the parcel (including picking up anddelivering the parcel 300). For instance, the total planned time for aparcel may be 0.0352778 hours (127 seconds). This can represent thetotal allowed time for picking up, handling, conveying, inspecting,unloading, loading, re-wrapping, delivering, and/or the like the parcel300 as it is transported through the carrier's transportation andlogistics network. In this example, the driver is allowed or allotted0.0007869 hours (2.83284 seconds) to pick up the parcel 300. As will berecognized, total planned times and additive planned times can be storedin association with various parcel information/data. Using thisinformation/data, the central computing entity 802 can determine andassign total planned times and additive planned times for dispatchplans, routes/flights, logical groupings, stops on routes/flights,parcels 300, and/or the like.

In one embodiment, the parcel information/data may also include trackinginformation/data (of various “tracking events”) corresponding to thelocation of the parcel 300 in the transportation and logistics network.To determine and reflect a parcel's movement, a parcel 300 identifierassociated with the parcel 300 may, for example, be scanned or otherwiseelectronically read at various points as the parcel 300 is transportedthrough the carrier's transportation and logistics network. Asindicated, these events may be referred to as tracking events. In oneembodiment, the latest or most-recent tracking events (e.g., trackinginformation/data) can associate the parcel 300 with the particularorigin entity, destination entity, bundle/container, vehicle, employee,location, facility, and/or the like.

B. User Profiles

In one embodiment, one or more users (e.g., consignors and/orconsignees) can register/enroll for an account, subscription, program,and/or similar words used herein interchangeably. In another embodiment,the user may be automatically enrolled/registered for the same. Aspreviously noted, a user may be an individual, a family, a familymember, a company, an organization, an entity, a department within anorganization, a representative of an organization and/or person, and/orthe like. In one embodiment, to register, a user (e.g., a user operatinga user computing entity 804) may access a webpage, mobile application,application, dashboard, browser, or portal of an entity that providesnotification/message services.

In one embodiment, as part of the enrollment/registration process, auser (e.g., a user operating a user computing entity 804) may berequested to provide information/data (e.g., including userinformation/data, biographic information/data, biometricinformation/data, geographic information/data, entity/entityinformation/data, payment information/data, and/or the like) by thecentral computing entity 802 (e.g., via the registration module). Theinformation/data may be manually input by a user; may be automaticallyprovided by allowing access to other accounts, such as Amazon.com,Facebook, Gmail, Twitter, PayPal, and/or the like; may be automaticallycollected by various computing entities (including automatic entityidentification); combinations thereof; and/or other techniques andapproaches. For instance, the biographic information/data may includethe user's name, such as a first name, a last name, a company name, anentity name, an organization name, and/or the like. The geographicinformation/data may also include one or more physical addresses orlocations associated with the user (e.g., street address, city, state,postal code, and/or country). The physical addresses or locations may beresidential addresses, commercial addresses, geocodes, latitude andlongitude points, virtual addresses, and/or the like. In one embodiment,the user information/data may include one or more electronic signaturesand signature formats for electronically signing documents, releases,and/or the like.

The user (e.g., consignor or consignee) may also provide one or morephysical addresses associated with the user (e.g., street address, city,state, postal code, and/or country) and/or one more geocodes to thecentral computing entity 802. For instance, Joseph Brown's primaryresidential address of 105 Main Street, Atlanta, Ga. 30309, USA, may beprovided to the central computing entity 802. Further, one or moresecondary residential addresses may also be provided to the centralcomputing entity 802 for association with Mr. Brown's account andprofile, such as 71 Lanier Islands, Buford, Ga. 30518, USA. As will berecognized, the residential addresses may include weekend residences,family member residences visited by the user, and/or the like.Additionally, the user (e.g., consignor or consignee) may also provideone or more business addresses associated with the user (e.g., streetaddress, city, state, postal code, and/or country) to the centralcomputing entity 802. For example, Mr. Brown may have a primary businessaddress of 1201 West Peachtree Street, Atlanta, Ga. 30309, USA. One ormore secondary business addresses may also be provided to the centralcomputing entity 802 for association with Mr. Brown's account andprofile, such as 101 South Tryon Street, Charlotte, N.C. 28280, USA; 950F Street, NW, Washington, D.C. 20004, USA; and 90 Park Avenue, New York,N.Y. 10016, USA. As will be recognized, the business addresses mayinclude various office locations for a single enterprise, multipleoffice locations for various enterprises, and/or the like. As will berecognized, the user (e.g., consignor or consignee) may provide otherbiographic and/or geographic information/data (e.g., geocodes) to adaptto various needs and circumstances.

In one embodiment, in addition to the physical addresses, the user(e.g., operating a user computing entity 804) may also input, request,or be automatically generated and assigned a “virtual address.” Thevirtual address can be a combination of alphanumeric characters toidentify a user or user profile. The virtual address can be stored bythe central computing entity 802 in association with the user's profile.For example, Joseph Brown (e.g., operating a user computing entity 804)may input a request for a unique virtual address such as BigBrown8675309or any other unique virtual address. In another embodiment, the centralcomputing entity 802 may automatically generate and assign a uniquevirtual address for the user, such as assigning virtual address1XR457RS7 to Joseph Brown. Such virtual addresses can be used by userswho do not want to (a) provide their physical addresses to merchants orother third parties, (b) have their physical addresses printed on labelsplaced on the exterior of parcels 300, (c) use geocoded points fordeliveries, (d) the like. For instance, this may enable a user (e.g.,consignor) to ship a parcel 300 using only BigBrown8675309; 1XR457RS7;or 33.7869128, −84.3875602 as the destination address (e.g., virtualaddress) using the appropriate carrier. Upon ingestion of the parcel 300into the carrier's transportation and logistics network, carrierpersonnel can read (e.g., manually or with the aid of an entity) thevirtual address on the parcel 300 (e.g., BigBrown8675309 or 1XR457RS7),look up the appropriate physical delivery address for the parcel 300based on the consignee's profile (e.g., search for the user profileassociated with the virtual address), and route/flight the parcel 300accordingly (including the use of automatic service schedules). Incertain embodiments, the parcel 300 may be routed only using the virtualaddress. That is, each parcel 300 is handled by carrier personnel, amobile station 105 (in communication with the central computing entity802) operated by the carrier personnel can cause display of theappropriate handling or routing instructions while masking the actualphysical delivery address. In other embodiments, however, once theparcel 300 with the virtual address is inducted into the carrier'stransportation and logistics network, carrier personnel may place alabel on the parcel 300 that indicates the physical delivery address(e.g., based on an address associated with the profile and/or automaticservice schedule).

In addition to the virtual address, the central computing entity 802 mayalso generate and store an internal user identifier in association withthe user profile, such as a global unique identifier (GUID) or auniversally unique identifier (UUID). For instance, in one embodiment,the user identifier may be a 128-bit value displayable as hexadecimaldigits with groups separated by hyphens. By way of example, the useridentifier for Joseph Brown may be 21EC2020-3AEA-4069-A2DD-08002B30309D.In one embodiment, a user identifier may be used to uniquely identify auser profile. In another embodiment, a user identifier may be used touniquely identify a given address (e.g., physical address or virtualaddress) associated with a user profile. In such an embodiment, if auser profile is associated with four addresses, the central computingentity 802 may generate and store four user identifiers in associationwith the user profile (or use one user identifier for all the addressesfor the user). The user identifier may also be stored in associationwith parcel information/data for a parcel 300 to associate the parcel300 (and its parcel information/data) with the (a) correct user (e.g.,user profile) and/or (b) correct address for a user. For instance, theparcel information/data for all parcels 300 corresponding to JosephBrown's user profile may be appended with the user identifier createdfor Joseph Brown. In various embodiments, using this approach allowsparcels 300 (and their parcel information/data) to be linked toappropriate user profiles. Thus, when Joseph Brown accesses his account,he can view all of his parcels 300 (e.g., those parcels 300 with parcelinformation/data appended with his user identifier (or otheridentifier)). Similarly, any actions for a parcel 300 or user can bepassed to the parcel information/data for the parcel 300 (includingcarrying out automatic service schedules). In other words, the useridentifier appended to the parcel information/data resolves to thecorresponding user profile/account and/or address. The parcelinformation/data may have multiple user identifiers appended—one or moreuser identifiers for the consignor and one or more user identifiers forthe consignee.

In one embodiment, the user information/data may include one or morecommunication formats for communicating with the user as part of his orher notification/message preferences. The communication formats mayinclude text notifications/messages (e.g., SMS, MMS), emailnotifications/messages, voice notifications/messages, videonotifications/messages (e.g., YouTube, the Vine), picturenotifications/messages (e.g., Instagram), social medianotifications/messages (e.g., private social media created internallyfor entities, business social media (e.g., Yammer, SocialCast), orpublic social media (e.g., Facebook, Instagram, Twitter), and/or avariety of other notifications/messages in various communicationformats. In addition to the one or more communication formats, the user(e.g., operating a user computing entity 804) can provide thecorresponding electronic destination addresses to be used in providinginformation/data associated with the notification/message services tothe user (e.g., email addresses, online handles, phone numbers,usernames, etc.). For instance, for text notifications/messages, theuser may provide one or more cellular phone numbers. For emailnotifications/messages, the user may provide one or more email addresses(to receive emails or notifications through specific accounts). And forvoice notifications/messages, the user may provide one or more cellularor landline phone numbers or other electronic destination addresses towhich audio files can be delivered. Additionally, in one embodiment,validation operations can be performed with respect to each inputelectronic destination address—to ensure accuracy. As will berecognized, a variety of other types of electronic destination addressescan be used to adapt to various needs and circumstances.

In one embodiment, entity/entity information/data, userinformation/data, physical address or location information/data, and/orthe like may be received, provided, obtained, detected, assigned,collected, requested, and/or similar words used herein interchangeablyas part of the registration/enrollment process. As will be recognized,entity/entity information/data may be collected for any number ofentities or entities for association with a user's account,subscription, program, and/or similar words used herein interchangeably.The entity/entity information/data may include one or more entity orentity identifiers—phone numbers, Subscriber Identity Module (SIM)numbers, Media Access Control (MAC) addresses, International MobileSubscriber Identity (IMSI) numbers, Internet Protocol (IP) addresses,Mobile Equipment Identifiers (MEIDs), unit identifiers (e.g., GPS unitidentifiers, UDiDs, mobile identification numbers (MINs), IMSI_S (ShortIMSIs), email addresses, usernames, GUIDs, Integrated Circuit CardIdentifiers (ICCIDs), electronic serial numbers (ESN), InternationalMobile Equipment Identities (IMEIs), Wi-Fi IDs, RFID tags, and/or thelike. The entity/entity information/data may include an entity's vendor,model, specification authority, version, components, softwarespecification and/or version, person associated with the entity, and/orthe like. The entity/entity information/data may be used to track,monitor, connect with, communicate with, and/or the like thecorresponding entities or entities.

In one embodiment, with the appropriate information/data, the centralcomputing entity 802 may create a user profile for the user via theenrollment/registration process. Accordingly, the central computingentity 802 may create, store, and/or have access to various userprofiles and/or information/data associated with the user profiles. Inaddition to at least the information/data described above, a userprofile may include one or more corresponding usernames, passwords,images, tokens, challenge phrases, reminders, and/or the like (referredto herein as credentials) for accessing accounts, applications,services, entities, and/or the like. As will be recognized, a variety ofother approaches and techniques can be used to adapt to various needsand circumstances.

In one embodiment, a user profile identifier may be used to uniquelyidentify a user profile. In another embodiment, a user profileidentifier may be used to uniquely identify a given address associatedwith a user profile. In such an embodiment, if a user profile isassociated with four addresses, the central computing entity 802 maycreate and store four user profile identifiers in association with theuser profile. The user profile identifier may also be stored inassociation with parcel information/data for a parcel 300 to associatethe parcel 300 (and its parcel information/data) with the (a) correctuser (e.g., user profile) and/or (b) correct address for a user.Moreover, the central computing entity 802 can associate parcelinformation/data for a parcel 300 with the corresponding user profile.This may include appending the parcel information/data with theappropriate user profile identifier (or other identifier correspondingto the user profile). For instance, the parcel information/data for allparcels 300 corresponding to Smith Co. Automotive's user profile may beappended with the user profile identifier (or other identifier) createdfor Smith Co. Automotive. In various embodiments, using this approachallows parcels 300 (and their parcel information/data) to be linked toappropriate user profiles. Thus, when a user at Smith Co. Automotiveaccesses its account, he or she can view all of his parcels 300 (e.g.,those parcels 300 with parcel information/data appended with his userprofile identifier (or other identifier)). Similarly, any actionsselected by the user for a parcel 300 can be passed to the parcelinformation/data for the parcel 300.

C. Pick-Up Points and Delivery Points

In one embodiment, pick-up and/or delivery points may be locations atwhich parcels can be picked up from and/or delivered to at a givenserviceable point 5901. Such locations can be stored in user profilesand/or as parcel information/data. Referring to FIG. 58, a deliverypoint may identify a location on a driveway, a location on a frontporch, a location inside of a garage, a location in yard, a location ontop of a building, and/or the like associated with a serviceable point5901. In one embodiment, the UAV 100 can use a primary delivery point(e.g., first desired delivery point/location 5902) for all deliveries asa default. Similarly, the UAV 100 can use one or more secondary deliverypoints (e.g., second desired delivery points/locations 5904) in theevent the primary delivery point (e.g., first desired deliverypoint/location 5902) is obstructed, is otherwise inaccessible, is notpreferred for a particular delivery or type of delivery, and/or thelike.

In addition to delivery points, a UAV landing point may be, for example,a location at which a UAV 100 can land for retrieval of parcels byconsignees. In one embodiment, a UAV landing point may be used, forexample, if a single address is associated with multipleprimary/secondary delivery points 5902, 5904 accessed by a singlelanding location (e.g., a mall with deliveries to multiple stores or anapartment complex with deliveries to multiple apartments). Thus, in oneexample, a UAV landing point may be where a UAV 100 can land formultiple consignees to retrieve parcels (e.g., landing at a mall orapartment complex). In another embodiment, a landing point can be usedwhen an automated release of a parcel is not available, for example,because of its size or configuration.

In one embodiment, different types of information/data sets can be usedto identify the various types of points at a serviceable point 5901. Forexample, in one embodiment, information/data associated with aserviceable point 5901 may include primary/secondary delivery point5902, 5904 information/data and or landing point information/data. Aswill be recognized, such information/data associated with the differentpoints can be collected or determined using a variety of techniques andmethods. For example, in one embodiment, each time a UAV 100 visits aprimary/secondary delivery point 5902, 5904 associated with aserviceable point 5901, a primary/secondary delivery point geocoordinate is collected or determined for the primary/secondary deliverypoint. The term primary/secondary delivery point geo coordinate mayrefer to, for example, information/data may include longitude andlatitude coordinates, geocodes, altitude, course, speed, distance, UTC,date information, and/or the like. This information/data may becollected, for example, via the UAV computing entity 808 (with orwithout the aid of the driver of the UAV 100). Similar information/datacan be collected from physical visits by carrier personnel, forinstance, to serviceable points 5901.

Operatively, in one embodiment, the UAV computing entity 808 providesthe functionality to maintain and process location information/data(such as latitude and longitude information/data) for locations to whichparcels are delivered or from which parcels picked up, for example.Accordingly, in one embodiment, the UAV computing entity 808 is adaptedto be used to gather geo coordinate samples (e.g., geocode, latitude andlongitude points, GPS readings, and/or the like) at each landing,delivery, or pick-up at a serviceable point 5901 over a period of time.More specifically, the UAV computing entity 808 can be configured tocollect geo coordinate samples continuously or upon determining theoccurrence of one or more configurable triggering events. Suchconfigurable triggering events may include, but are not limited to:landing events, obstacle detection events, parcel release events,failure events, scan or other read events, communication or confirmationevents, notification events, delivery events, and/or the like. Thus, foreach delivery point and landing point at a serviceable point 5901, oneor more geo coordinate samples (e.g., GPS readings) may be taken by theUAV computing entity 808 in response to various triggering events.

As indicated, in one embodiment, the UAV computing entity 808 isconfigured to continuously and/or periodically store geo coordinatesamples, regardless of whether a triggering event has occurred. This maybe beneficial since geo coordinates may not always be available at anygiven time since, for example, a GPS signal could be temporarily blockedby a nearby obstruction. Thus, for instance, if a triggering eventoccurs at a time when a geo coordinate is not immediately obtainable,the last known geo coordinate (or in some embodiments the next geocoordinate) can be used. In such embodiments, the UAV computing entity808 may store information/data about the time of the geo coordinatesample and the time of the associated triggering event so that thegeographic information/data database provider may use theinformation/data in determining the accuracy of the geo coordinatesamples.

The geo coordinate samples can be provided to the geographicinformation/data database, which, after an appropriate number of geocoordinate samples associated with a primary/secondary delivery point,processes the sample geo coordinates and creates or updates theprimary/secondary delivery point geo coordinate for the serviceablepoint 5901. For example, the geographic information/data database may beconfigured to require two, three, and/or more consistent sample geocoordinates associated with a primary/secondary delivery point 5902,5904 before creating or updating a primary/secondary delivery point geocoordinate for the serviceable point 5901.

In various embodiments, the information/data sets for the points need tobe stored and accessed for route/path determination and optimization. Invarious embodiments, the primary/secondary delivery point 5902, 5904information/data may be stored in a variety of ways—including as part ofa user profile, parcel information/data, and/or a serviceable point 5901profile. For example, a serviceable point 5901 object (e.g., datastructure) may be used to store (a) the address of the serviceable point5901, (b) the latitude and longitude of a primary/secondary deliverypoint 5902, 5904 associated with the serviceable point 5901 (e.g.,primary/secondary delivery point geo coordinate), (c) the latitude andlongitude type (e.g., latitude and longitude of a primary/secondarydelivery point 5902, 5904 or latitude and longitude of a UAV landingpoint) of the primary/secondary delivery point 5902, 5904 associatedwith the serviceable point 5901, (d) the latitude and longitude of astreet network connection point 400 associated with the serviceablepoint 5901 (e.g., street network connection point geo coordinate), (e)obstacles at the serviceable point 5901, (f) delivery history at theserviceable point 5901, and/or the like.

D. Grouping-Based Load and Takeoff Operations

In one embodiment, the central computing entity 802 can create/generatedispatch plans for carrying out the pick-ups and/or deliveries for theUAV computing entity 808 to pick-up points and/or delivery points at oneor more serviceable points 5901. Dispatch plans are well known and areused daily by various carriers. In general, dispatch plans are groups ofroutes/flights planned to be dispatched together along with theirassociated delivery and pick-up assignments. Dispatch plans may alsoindicate how each primary parcel delivery vehicle 10 should be loadedand/or how each route/flight should be carried out. FIGS. 51, 52, and 53include various territories, routes/flights, serviceable points 5901associated with a territory (e.g., geographic area) or route/flight, andassigned pick-ups and deliveries for serviceable points 5901 for thesame. A route/flight is generally a one or more address ranges forserviceable points 5901 with associated service levels assigned to asingle service provider (e.g., carrier delivery personnel). Eachroute/flight usually includes a trace, which is a predefined path forcarrying out one or more deliveries. A delivery order listing then is alisting of address ranges, addresses, and/or parcels 300 for serviceablepoints 5901 that follows the trace for the route/flight to visit performthe assigned pick-ups and/or deliveries for serviceable points 5901.Through an appropriate interface, dispatch plans can be compared againstalternative dispatch plans to load balance and otherwise adjust thevarious dispatch plans for a given geographic area, service center,route/flight, and/or the like. U.S. Pat. No. 7,624,024 entitled Systemsand Methods for Dynamically Updating a Dispatch Plan, filed Apr. 18,2005 provides a general description of dispatch plans and how theseplans may be generated and updated. This may include dynamicallyupdating dispatch plans to add, remove, or update pick-ups and/ordeliveries for serviceable points 5901. U.S. Pat. No. 7,624,024 isincorporated herein in its entirety by reference.

So that the parcels can be readily accessed for loading to a UAV 100based on the delivery order listing, each parcel can be assigned aload/storage position in the primary parcel delivery vehicle 10. In oneembodiment, each load/storage position may be associated with a uniqueload/storage position. For instance, each parcel may be assigned asequence number between 0001-9999 (a number within the sequence range)based upon the load/storage position. In another example, each parcelmay be assigned a grid position A1-Z99. As will be recognized, a varietyof other approaches and techniques can be used to adapt to various needsand circumstances.

In one embodiment, the load/storage position can be stored inassociation with the corresponding parcel information/data. Theload/storage position can be provided via an interface, printed on apre-load label to assist in loading the vehicle, and/or implementedthrough a variety of other techniques and approaches. In one embodiment,the load/storage position (e.g., 0001-0050 or A1-A30) can be a logicalgrouping. A logical grouping may comprise a plurality of parcels thatare to be delivered within a planned time (e.g., an estimated timeperiod/frame of one another, such as 15 minutes, 1 hour, 2 hours, 4hours, day, and/or the like). For instance, logical groupings may bebased on routes/flights, route/flight portions, neighborhood names, zipcodes, zip code+4, geographic areas, longitude and latitude ranges,geocodes, geographic descriptors, zones of confidence, geofences, and/orthe like. As will be recognized, in one embodiment, each route/flightmay comprise one or more logical groupings and/or logical groupingidentifiers. Each logical grouping may correspond to a specific plannedtime (e.g., estimated pick-up/delivery time or window). For instance, alogical grouping may be associated with a planned time for deliveringall of the parcels in the logical grouping: 15 minutes, 30 minutes, 1hour, 2 hours, and/or the like. The estimated pick-up/delivery windowmay indicate the estimated amount of time to deliver all parcels of thelogical grouping. For instance, if the planned time for the logicalgrouping is 1 hour, this may indicate that the parcels 300 for thelogical grouping will be delivered within the next hour from that point.That is, the estimated pick-up/delivery window or time can be used toindicate when or within what timeframe the corresponding parcels will bedelivered. If the current time is 1:00 pm EST and the planned time is 1hour, the estimated pick-up/delivery window for all parcels will be 1:00pm EST to 2:00 pm EST. The logical groupings can also be stored inassociation with the parcel information/data. In another embodiment, aspecific information/data field or portion of an information/data fieldin the parcel information/data may already be designated as a logicalgrouping identifier. For example, the logical grouping identifier may bea portion of the shipment identifier, all or a portion of a zip codefield, a load/storage position, a route/flight, a route/flight portion,all or a portion of a sequence number, a geographic descriptor, and/orthe like. By using such logical groupings, grouped takeoffs for UAVs 100can be coordinated within specific planned time and/or pick-up/deliverywindows.

In one embodiment, a variety of computing entities (e.g., deliveryvehicle computing entity 810, central computing entity 802, mobilecarrier computing entity 806, and/or the like) can determine or receiveinput that a parcel is about to be delivered, is being delivered, or hasjust been delivered (Block 4700 of FIG. 50). For instance, in oneembodiment, the mobile carrier computing entity 806 is configured toreceive input (e.g., via the user interface) that indicates a variety ofservice dynamics, such as delivery-related or vehicle-related activitiesor occurrences. For example, in various embodiments, the user interfaceis configured to permit a driver to indicate the following servicedynamics: (a) that a delivery stop has commenced (e.g., by pressing abutton indicating that the driver has arrived at a deliverypoint/location and commenced the delivery process, scanning orinterrogating a parcel), (b) that a delivery stop has ended (e.g., bypressing a button indicating that the driver has completed the deliveryand is now leaving the delivery location), (c) that a particular bill oflading and its associated freight or packages have been picked up ordelivered (e.g., by entering or scanning a tracking number or code, orotherwise identifying one or more bills of lading associated withfreight or packages that have been picked up or delivered), (d) thenumber of units picked up or delivered at a stop (e.g., by manuallyentering a numerical value), (e) the weight of packages or freightpicked up or delivered at a stop (e.g., by manually entering a numericalvalue), (f) that a lunch or break period has commenced or ended (e.g.,by pressing a button indicating that the start or stop of a break orlunch), (g) that a particular delay encountered by a driver hascommenced or ended (e.g., by entering a code or otherwise identifying atype of delay that a driver has encountered—such as waiting for freight,caught in traffic, fueling a vehicle, waiting at train tracks, waitingat security, waiting for bill of lading—and pressing a button indicatingthat the identified delay has started or stopped), (h) that the driverhas begun a work day and is on the clock (e.g., at a shipping hub andbefore starting the delivery vehicle computing entity 810), (i) that thedriver has ended a work day and is off the clock, (j) that the driverand vehicle have entered a particular area (e.g., the property of ashipping hub, a designated delivery area or other work area), and/or (k)that the driver and vehicle have exited a particular area (e.g., theproperty of a shipping hub, a designated delivery area or other workarea).

In one embodiment, in response to receiving input indicating that adelivery is about to occur or has occurred, the mobile carrier computingentity 806 may capture service information/data and/or parcelinformation/data in a computer readable format (Block 4700 of FIG. 50).After receiving input capturing the service information/data and/orparcel information/data, an appropriate computing entity can determinewhether the parcel information/data is part of the current logicalgrouping (4702 of FIG. 50). For the first delivery for the day (or othertime period, such as shifts or after breaks), the appropriate computingentity will determine that the parcel is not part of the current logicalgrouping as it is the first logical grouping being delivered for the dayor time period/frame (e.g., the current logical grouping value is nulluntil it is set by the first delivery of the day or time period). Oncethe current logical grouping value has been set for the day (or timeperiod), the appropriate computing entity can store an indicator of thecurrent logical grouping based on the last parcel delivered.Correspondingly, each time the mobile carrier computing entity 806 (orother appropriate computing entity) records a stop as being completed(e.g., a parcel as being delivered), the mobile carrier computing entity806 can store the logical grouping of that parcel (e.g., the mostrecently delivered parcel) as the current logical grouping. Forsubsequent parcels, the appropriate computing entity (e.g., deliveryvehicle computing entity 810, central computing entity 802, mobilecarrier computing entity 806, and/or the like) can compare the logicalgrouping for the parcel that is about to be or has been delivered withthe logical grouping that is indicated as being the current logicalgrouping. To do so, an appropriate computing entity identifies thecurrent logical grouping and the logical grouping for the parcel that isabout to be or has been delivered.

Responsive to determining that a parcel is part of the current logicalgrouping, the appropriate computing entity does not take any action.Rather, the appropriate computing entity (e.g., delivery vehiclecomputing entity 810, central computing entity 802, mobile carriercomputing entity 806, and/or the like) waits for input indicating that adifferent parcel is about to be or has been delivered (e.g., the processreturns to Block 4700 of FIG. 50).

Responsive to determining that a parcel is not part of the currentlogical grouping, in one embodiment, the mobile carrier computing entity806 can present a customized, interactive interface to the carrierpersonnel (Blocks 4704, 4706, and 4708 of FIG. 50). In one embodiment,the customized, interactive interface may provide the carrier personnelwith the ability to confirm whether the parcel is part of a new logicalgrouping. Responsive to input received via the customized, interactiveinterface indicating that the parcel is not part of a new logicalgrouping, an appropriate computing entity (e.g., delivery vehiclecomputing entity 810, central computing entity 802, mobile carriercomputing entity 806, and/or the like) can automatically initiate atimer for a configurable time period/frame (e.g., 30 seconds, 2 minutes,5 minutes, 10 minutes, and/or the like) to bypass the operations inBlocks 4700-4708 of FIG. 50. The automated timer provides for amechanism to limit the burden on carrier personnel with repeatedrequests (e.g., for each parcel being delivered) to confirm logicalgroupings in a short period of time (e.g., for every parcel deliveredwithin a short period of time). Once the time period/frame of haselapsed (Block 4712 of FIG. 50), the process can return to Block 4700 ofFIG. 50. Use of the automated timer also reduces processing by notchecking each parcel that is for pick-up or delivery, but allows theprocessing element to be used for other processing and/or tasks.

Responsive to input received via the customized, interactive interfaceindicating that the parcel is part of a new logical grouping, anappropriate computing entity (e.g., delivery vehicle computing entity810, central computing entity 802, mobile carrier computing entity 806,and/or the like) can automatically initiate the loading of the parcels300 for the new logical grouping for takeoff and delivery via one ormore UAVs 100 (Block 4708 of FIG. 50).

In an embodiment in which a timer is utilized, if a parcel is deliveredduring the time period/frame of the timer, the next delivery outside ofthe time period/frame from the logical grouping will be detected atBlock 4700 since the current logical grouping indicator will not havebeen updated since the corresponding operations have been bypassed.Thus, if parcels are delivered during the time period/frame of thetimer, other parcels in the logical grouping will be detected togenerate and transmit corresponding notifications/messages.

E. Geofence-Based Load and Takeoff Operations

In one embodiment, an appropriate computing entity can identify ordefine one or more geofences, such as defining a geofence around ageographic area. The geofences may be defined to surround a definedgeographic area, such as surrounding countries, regions, states,counties, cities, towns, interstates, roads, streets, avenues, tollroads, zip codes, area codes, ways, exit and entrance ramps, deliveryroutes, route/flight patterns, neighborhoods, shopping centers, off-roadareas (e.g., areas without paved roads), private land areas, parkinglots (e.g., at malls or other establishments), driveways, and/or thelike. The geofences may be defined, for example, by the latitude andlongitude coordinates associated with various points along the perimeterof the geographic area. Alternatively, geofences may be defined based onlatitude and longitude coordinates of the center, as well as the radius,of the geographic area. Geofences may be as large as an entire country,region, state, county, city, or town (or larger). The geographic areas,and therefore the geofences, may be any shape including, but not limitedto, a circle, square, rectangle, an irregular shape, and/or the like.Moreover, the geofenced areas need not be the same shape or size.Accordingly, any combination of shapes and sizes may be used inaccordance with embodiments of the present invention. Similarly, ageofence may overlap or reside wholly within another geofence.

In one embodiment, once at least one geofence has been defined, thecoordinates (or similar methods for defining the geofenced areas) andcorresponding geofence identifier may be stored in a map/geographicinformation/data database accessible by a variety of computing entities.Thus, as the primary parcel delivery vehicle 10 and/or UAV 100 entersand exits the one or more defined geofences, an appropriate computingentity can monitor the location of the primary parcel delivery vehicle10 and/or UAV 100 and trigger/initiate certain events based on thelocation.

So that the parcels can be readily accessed for loading to a UAV 100based on geofences, each parcel 300 and/or parcel carrier 200 can beassigned a geofence identifier (indicating the geofence in which itshould be delivered) and stored in the primary parcel delivery vehicle10 proximate to other parcels associated with the same geofenceidentifier. In one embodiment, each geofence may be associated with aplanned time for delivering all of the parcels in the geofence: 15minutes, 30 minutes, 1 hour, 2 hours, and/or the like. The estimatedpick-up/delivery window may indicate the estimated amount of time todeliver all parcels in the geofence. For instance, if the planned timefor the geofence is 1 hour, this may indicate that the parcelsassociated with the geofence will be delivered within the next hour oncethe geofence is entered. That is, the estimated pick-up/delivery windowor time can be used to indicate when or within what timeframe thecorresponding parcels will be delivered. If the current time is 1:00 pmEST and the planned time is 1 hour, the estimated pick-up/deliverywindow for all parcels will be 1:00 pm EST to 2:00 pm EST. The geofenceidentifier can also be stored in association with the parcelinformation/data. In another embodiment, a specific information/datafield or portion of an information/data field in the parcelinformation/data may already be designated as a geofence identifier. Forexample, the geofence identifier may be a portion of the shipmentidentifier, all or a portion of a zip code field, a load/storageposition, a route/flight, a route/flight portion, all or a portion of asequence number, a geographic descriptor, and/or the like. By using suchgeofences, grouped loads and takeoffs for UAVs 100 can be coordinatedwithin specific planned time and/or pick-up/delivery windows.

In one embodiment, with one or more geofenced areas (e.g., geofences)defined, the location of the primary parcel delivery vehicle 10 and/orUAV 100 can be monitored. Generally, the location of the primary parceldelivery vehicle 10 and/or UAV 100 can be monitored by any of a varietyof computing entities, including the delivery vehicle computing entity810, UAV computing entity 808, the mobile carrier computing entity 806,the central computing entity 802, and/or the like. For example, as notedabove, a location at a particular time may be determined with the aid oflocation determining elements/components. By using the primary parceldelivery vehicle's 10 and/or UAV's 100 location, an appropriatecomputing entity can determine, for example, when the primary parceldelivery vehicle 10 and/or UAV 100 enters a defined geofence.

In one embodiment, in response to (e.g., after) a determination that aprimary parcel delivery vehicle 10 and/or UAV 100 has entered a definedgeofenced area, an appropriate computing entity can initiate thepick-up/delivery of the parcels associated with the geofence identifierfor the entered geofence. That is, a corresponding computing entity canidentify all parcels in the dispatch plan associated with the geofencedidentifier for loading and taking off via a UAV 100. In particular, oncethe vehicle 10 and/or UAV 100 has entered a defined geofenced area, UAVs100 may be dispatched from the vehicle 10 to deliver parcels 300 todelivery/pick-up points/locations positioned within the geofenced area.

In one embodiment, after the primary parcel delivery vehicle 10 and/orUAV 100 has entered the geofenced area, the location of the primaryparcel delivery vehicle 10 and/or UAV 100 can continue to be monitoredby any of a variety of computing entities. By using the primary parceldelivery vehicle's 10 and/or UAV's 100 location, a computing entity candetermine, for example, when the primary parcel delivery vehicle 10and/or UAV 100 exits the defined geofenced area. As described, this mayinclude using various location determining elements/components. Inanother embodiment, in response to (e.g., after) a determination that aprimary parcel delivery vehicle 10 and/or UAV 100 has exited the definedgeofenced area, an appropriate computing entity can stop the delivery ofparcels to the exited geofence (e.g., based on the geofence identifier)and/or provide a notification/message to the mobile carrier computingentity 806 and/or central computing entity 802 regarding the status ofeach parcel to be delivered using a UAV 100 within the geofence.

F. Route/Flight-Based Load and Takeoff Operations

In embodiments, in conjunction with or independently of the logicalgroup-based and geofence-based load and takeoff methods described above,the UAVs 100 may be loaded to and may take off from the vehicle 10according to a dispatch plan based on a route/flight (e.g., trace) orpredetermined/configurable path for carrying out one or moredeliveries/pick-ups. As described above, each route/flight usuallyincludes a trace, which is a predefined path for carrying out one ormore pick-ups and/or deliveries. A delivery order listing is a listingof address ranges, addresses, and/or parcels 300 for serviceable points5901 that follows the trace to perform the assigned pick-ups and/ordeliveries for serviceable points 5901. Through an appropriateinterface, dispatch plans can be compared against alternative dispatchplans to load balance and otherwise adjust the various dispatch plansfor a given geographic area, service center, route/flight, and/or thelike. In such embodiments, takeoffs can be triggered based on time,location, pick-ups and/or deliveries completed, position in the trace,and/or the like.

Furthermore, in such embodiments, messages/notifications can be providedto user computing entities 804 based on the progress of a vehicle 10and/or UAV 100 through a predetermined/configurable route/flight. Themessage/notification criteria may be based on the estimated time ofarrival of carrier at the serviceable point 5901. For example, theconsignor/consignee may seek to receive a message when the vehicle 10and/or the UAV 100 is approximately 1 hour away, 30 minutes away, 15minutes away and/or 5 minutes away. In this case, central computingentity (and/or the user computing entity 804) may identify the number ofstops needing to be made before arriving at the specificconsignor/consignee's serviceable point 5901 and applying apredetermined/configurable stop time estimate to calculate an estimatedtime of arrival at the consignor/consignee's serviceable point 5901(e.g., number of stops*standard stop duration). In some embodiments, theestimate may also include estimated travel time between the remainingstops (e.g., ETA calculated by navigations software, distance ofanticipated route*average speed, etc.). In further embodiments, thecentral computing entity 802 may use historical information/dataregarding service times and/or travel times between stops to arrive atan estimated arrival time at the user's serviceable point. Depending onthe user's preferences in the corresponding user profile, this processmay be repeated with messages being sent when the vehicle 10 or UAV 100is 30, 15, and/or 5 minutes away. The central computing entity 802(and/or the user computing entity 804) may also send theconsignor/consignee an arrival message when the vehicle 10 and/or theUAV 100 is approaching and/or arrives at the consignor/consignee'sserviceable point 5901. The individual messages may be sent via the sameprotocol or under different protocols according to the preferences ofthe user and/or carrier (e.g., countdown messages by text). As will berecognized, a variety of other approaches and techniques can be used toadapt to various needs and circumstances.

G. Pre-Flight Condition Operations

Referring to FIG. 54, one embodiment of operations for determining if aparcel 300 is suitable for delivery via UAV 100 is schematicallydepicted. For example, prior to attaching a parcel carrier 200 to aparcel 300 at the intermediate location 601 (FIG. 32), the centralcomputing entity 802, or another suitable computing entity, maydetermine whether conditions are suitable for delivering the parcels 300via UAV 100. In a first step 5402, the central computing entity 802detects a wind speed associated with a predetermined/configurable area.In embodiments, the predetermined/configurable area includes ageographic area in which parcels 300 may be delivered and/or picked upvia UAV 100, and may include one or more geofenced areas. The centralcomputing entity 802 may detect the wind speed conditions, such as byaccessing weather forecasts from the internet via the network 800 (e.g.,wind speeds at the current time and/or projected time of delivery).Alternatively, vehicles 10 may be equipped with one or more wind speeddetection devices, such as an anemometer that is communicatively coupledto an associated delivery vehicle computing entity 810, and the centralcomputing entity 802 may receive detected wind speed conditions for thepredetermined/configurable area from the delivery vehicle computingentity 810 of a vehicle 10.

In a second step 5404, the central computing entity 802 determines ifthe wind speed is below a predetermined/configurable wind speedthreshold. If the detected wind speed conditions are not below thepredetermined/configurable wind speed threshold, then the centralcomputing entity 802 proceeds to step 5412 and provides instructions toprepare the parcels 300 within the intermediate location 601 forconventional delivery (e.g., without the use of a UAV 100). Inembodiments, the predetermined/configurable wind speed threshold may be30 miles per hour (mph). In other embodiments, thepredetermined/configurable wind speed threshold may be 25 mph. In stillother embodiments, the predetermined/configurable wind speed thresholdmay be 15 mph.

If at step 5404, the detected wind speed is below thepredetermined/configurable wind speed threshold, then the centralcomputing entity 802 proceeds to step 5406, and detects precipitationconditions for the predetermined/configurable area. In embodiments, thecentral computing entity 802 may detect precipitation conditions withinthe predetermined/configurable area. For example, the central computingentity 802 may detect current and forecasted precipitation conditionswithin the predetermined/configurable area, such as by accessing weatherforecasts from the internet via the network 800.

The central computing entity 802 then proceeds to step 5408, anddetermines if the precipitation conditions within thepredetermined/configurable area are below a predetermined/configurableprecipitation threshold. If the detected precipitation conditions arenot below the predetermined/configurable precipitation threshold, thenthe central computing entity 802 proceeds to step 5412 and providesinstructions to prepare the parcels 300 within the intermediate location610 for conventional delivery. If the detected precipitation conditionsare below the predetermined/configurable precipitation threshold, thenthe central computing entity 802 proceeds to step 5410 and providesinstructions to prepare the parcels 300 within the intermediate locationfor delivery via UAV 100. The predetermined/configurable precipitationthreshold may be based on a percent chance of precipitation within thepredetermined/configurable area (e.g., a percent chance of precipitationwithin the predetermined/configurable area on a specific day), or thepredetermined/configurable precipitation threshold may include adetected precipitation event (e.g., rain, sleet, snow, etc.) within apredetermined/configurable distance of the predetermined/configurablearea. For example, the predetermined/configurable precipitationthreshold may be a forecast indicating a 10% chance of precipitationwithin the predetermined/configurable area. In other embodiments, thepredetermined/configurable precipitation threshold may be a forecastindicating a 20% chance of precipitation within thepredetermined/configurable area. In other embodiments, thepredetermined/configurable precipitation threshold may include anindication of a precipitation event detected within 20 miles of thepredetermined/configurable area. In still other embodiments, thepredetermined/configurable precipitation threshold may include anindication of a precipitation event detected within 40 miles of thepredetermined/configurable area.

Accordingly, the central computing entity 802 may provide instructionsto prepare parcels 300 within the intermediate location 601 forconventional delivery or for delivery via UAV 100 based on theabove-described and/or various other weather/environmental conditions.As may be appreciated, it may be difficult to operate UAVs 100 inadverse weather/environmental conditions, such as in high winds, inprecipitation, and/or in low or high temperatures. Operation of the UAVs100 in such conditions may increase the chances for unsuccessfuldelivery of the parcel 300, and may result in damage to the parcel 300and/or the UAV 100, which may generally reduce user satisfaction and mayincrease operating costs. Accordingly, by providing an indication thatthe parcels 300 should be prepared for conventional delivery based onthe detection of adverse weather/environmental conditions, the centralcomputing entity 802 may assist in reducing operating costs and inensuring successful delivery of the parcels 300.

H. Parcel Engagement Operations

Referring collectively to FIGS. 32 and 55, the perspective view of theintermediate location 601 and one embodiment of operations forassociating a parcel 300 with a parcel carrier 200 are schematicallydepicted, respectively. In a first step 5502, a parcel 300 isscanned/read/received by the parcel identification unit 632, and theparcel identification unit 632 may read the parcel identifier of theparcel 300. In a second step S504, the parcel identification unit 632may communicate the parcel identifier to the central computing entity802. In a third step 5506, the parcel carrier identification unit 613scans a parcel carrier 200 positioned on the robot 612 as the robot 612installs the parcel carrier 200 to the parcel carrier clamps 622. In afourth step 5508, the parcel carrier identification unit 613communicates the scanned/read/received parcel carrier 200 to the centralcomputing entity 802. In a fifth step 5508, the central computing entity802 associates the scanned/read/received parcel identifier with thescanned/read/received parcel carrier identifier. As may be appreciated,the parcel carrier 200 and the associated parcel 300 may be connected toone another at the engagement clamping mechanism 634, which is spacedapart from the parcel identification unit 632 and the parcel carrieridentification unit 613 of the robot 612. Accordingly, when associatingthe parcel carrier identifier with the parcel identifier, the centralcomputing entity 802 may consider and accommodate the parcel carriers200 positioned between the parcel carrier identification unit 613 andthe engagement clamping mechanism 632, as well as the parcels 300positioned between the parcel identification unit 632 and the engagementclamping mechanism 634.

By associating the parcels 300 with the parcel carriers 200 that areattached to the parcels 300, the central computing entity 802 may trackand monitor the position and progress of parcels 300 and associatedparcel carriers 200 throughout a delivery process.

Reference will now be made to methods for supplying parcel carriers 200within the vehicle 10 to the UAV 100, and operations for the deliveryand pick-up of parcels 300 via UAV 100.

I. Remote User Authorization and Takeoff Operations

Referring to FIG. 56, one embodiment of operations for loading a parcelcarrier 200 to a UAV 100 is schematically depicted. As described above,the delivery vehicle computing entity 810 is communicatively coupled tothe central computing entity 802, and may be communicatively coupled tothe robot processor 522 and the conveyor controller 460 of the vehicle10. In a first step 5601, the delivery vehicle computing entity 810determines if the supply position sensor 450 a indicates if a UAV 100 ispositioned within the supply region 408. If the delivery vehiclecomputing entity 810 does not receive a signal from the supply positionsensor 450 a indicating the UAV 100 is positioned within the supplyregion 408, the delivery vehicle computing entity 810 remains at step5602. If the delivery vehicle computing entity 810 receives a signalfrom the supply position sensor 450 a indicating that a UAV 100 ispositioned within the supply region 408, the delivery vehicle computingentity 810 proceeds to step 5604 and commands the robot 500 to retrievea parcel carrier 200 from the rack 30 within the vehicle 10.

In an optional second step 5602, the delivery vehicle computing entity810 determines and a parcel carrier 200 for dispatch. As describedabove, parcel carriers 200 (and the associated parcels 300) may bedispatched from the vehicle 10 based on logical groupings and/or basedon the position of the vehicle 10, such as when the vehicle 10 ispositioned within a geofenced area. Upon selecting a parcel carrier 200for dispatch, the delivery vehicle computing entity 801 proceeds to step5603. At step 5603, the delivery vehicle computing entity 810 determinesif a confirmation has been received from the user computing entity 804,indicating that the consignor/consignee would like the delivery/pick-upto be performed via UAV 100. For example, in some embodiments, prior todispatching a parcel carrier 200 (and associated parcel 300 whenperforming a delivery) from the vehicle 10, the delivery vehiclecomputing entity 804 may send a notification to the user computingentity 804. The notification may invite the consignor/consignee toprovide an input via the user computing entity 804 confirming that theconsignor/consignee would like a delivery/pick-up to be performed viaUAV. If the delivery vehicle computing entity 810 does not receive aconfirmation from the user computing entity 808, the delivery vehiclecomputing entity 810 may return to step 5602 and determine anotherparcel carrier 200 for dispatch. In this way, the delivery vehiclecomputing entity 810 may receive confirmation from a consignor/consigneethat the consignor/consignee would like to have a delivery/pick-upperformed via UAV 100 prior to dispatch of the UAV 100 from the vehicle10. If the delivery vehicle computing entity 810 receives a confirmationfrom the user computing entity 808, the delivery vehicle computingentity 810 proceeds to step 5604 and commands the robot to retrieve theparcel carrier 200 from the rack 30.

The delivery vehicle computing entity 810 then proceeds to step 5606,and commands the robot 500 to install the parcel carrier 200 to the UAVchassis 110. Upon installing the parcel carrier 200 to the UAV chassis110, the delivery vehicle computing entity 810 may additionally provideinformation/data to the UAV computing entity 804 indicating thedestination of the parcel carrier 200 (e.g., a coordinate location ofthe delivery/pick-up point/location to which the parcel carrier 200 isto be transported).

Once the parcel carrier 200 is installed to the UAV chassis 110, thedelivery vehicle computing entity 810 proceeds to step 5608, and movesthe UAV to the takeoff end 402. Once moved to the takeoff end 402, thepropulsion members 102 of the UAV 100 may be engaged, and the UAV 100may depart from the vehicle 10.

The operations described above with respect to FIG. 56 may be performedto prepare UAVs 100 for both deliveries, in which the parcel carrier 200installed to the UAV 100 is coupled to a parcel 300. The operations mayalso be performed to prepare UAVs 100 for pick-ups, in which the parcelcarrier 200 installed to the UAV 100 is not coupled to a parcel 300, butis rather configured to pick up a parcel 300 from a serviceable point.

J. Navigation of UAV for Pick-Up/Delivery

In various embodiments, UAVs 100 can operate autonomously. In anautonomous embodiment, UAVs 100 may navigate between vehicles 10 andserviceable points 5901 along predetermined/configurable flightroutes/paths. A predetermined/configurable flight path may include adirect line of flight between the vehicle 10 and the serviceable point5901. The UAV 100 may proceed along a direct line between a vehicle 10and a serviceable point 5901, and the UAV 100 may deviate from thepredetermined/configurable flight path in response to receiving anindication of an object or obstacle in the flight path from the flightguidance sensor 166. In some embodiments, the predetermined/configurableflight path may include one or more waypoints (e.g., geocodes or geocoordinates), or one or more geographic locations that the UAV 100 willtravel to between the vehicle 10 and the serviceable point 5901. Thewaypoints may be determined to provide an efficient flight path betweenthe vehicle 10 and the serviceable point 5901 (e.g., minimizing flighttime), and be determined based on known obstacles that would prevent adirect flight path between the vehicle 10 and the serviceable point 5901(e.g., buildings, power lines, etc.).

Alternatively, in some embodiments, the flight and operations of the UAV100 may be remotely and manually controlled, such as through the mobilecarrier computing entity 806, the central computing entity 802, and/orthe delivery vehicle computing entity 810. As will recognized, a varietyof other approaches and techniques can be used to adapt to various needsand circumstances.

Referring to FIG. 57, one embodiment of operations of the UAV 100 afterthe UAV 100 has departed from the vehicle 10 is schematically depicted.In a first step 5702, the UAV 100 navigates from the takeoff end 402 ofthe vehicle 10 to a desired serviceable point 5901. In embodiments, theUAV 100 navigates to a desired serviceable point based oninformation/data associated with the parcel carrier 200.

In some embodiments, the delivery vehicle computing entity 810 and/orthe UAV computing entity 808 may provide a notification/message to theuser computing entity 804 indicating that the UAV 100 has departed fromthe vehicle 10. The UAV computing entity 808 may also provide anindication to the user computing entity 804 indicating the estimatedtime of arrival of the UAV 100 to the serviceable point based on theposition of the UAV 100 with respect to the serviceable point. Furtherin some embodiments, the UAV computing entity 808 may transmit alive-feed/stream for display on the user computing entity 804 of theroute/flight of the UAV 100, such as may be captured by the one or morecameras 168.

At step 5704, if the parcel carrier 200 is scheduled for a pick-up, theUAV computing entity 808 proceeds to step 5706 and initiates a pick-upsequence. If the parcel carrier 200 is not scheduled for a pick-up, thenthe UAV computing entity 808 proceeds to step 5708 and initiates adelivery sequence. Operational steps for the delivery sequence (e.g.,step 5708) and the pick-up sequence (e.g., step 5706) are described ingreater detail herein.

Referring to FIG. 58, a front view of a UAV 100 at a serviceable point5901 is schematically depicted. In embodiments, a consignee or user mayrequest delivery to or pick-up of the parcel 300 at a serviceable point5901, which may include a home, business, or other location at which theconsignee wishes the parcel 300 to be delivered. The consignor/consigneemay further request that the parcel 300 is delivered to one or morepreferred delivery/pick-up points/locations at the serviceable point5901. As one example, the consignee may request that the parcel isdelivered to a first desired delivery point/location 5902 or analternate second desired delivery point/location 5904 at the serviceablepoint 5901, where the first desired delivery point/location 5902 isspaced apart from the second desired delivery point/location 5904. Inthe embodiment depicted in FIG. 58, the first the first desired deliverypoint/location 5902 is positioned in a front area of the serviceablepoint 5901 (e.g., in the front yard and/or the like), while the seconddesired delivery point/location 5904 is positioned in a rear area of theserviceable point 5901 (e.g., in the back yard and/or the like).Alternatively, the first desired delivery point/location 5902 and thesecond desired delivery point/location 5904 may be positioned at anylocations of the serviceable point 5901 suitable to receive a parcel300, for example, the roof of a structure, a porch, a driveway, and/orthe like. In some embodiments, the first desired delivery point/location5902 and/or the second desired delivery point/location 5904 may bepositioned within a portion of the serviceable point 5901 havingrestricted access. For example, the first desired deliverypoint/location 5902 and/or the second desired delivery point/location5904 may be positioned within a garage 5906 of the serviceable point5901, where the garage 5906 is selectively accessible through a garagedoor 5908. In embodiments, the position of the desired deliverypoints/locations at the serviceable point 5901 may be associated with auser profile, such that the desired delivery points/locations may bere-used for subsequent deliveries to the serviceable point 5901.

In embodiments, the UAV computing entity 808 may communicate with theuser computing entity 802 so that the UAV 100 may gain access to thegarage 5906 (or access the same via user profile). For example, the UAVcomputing entity 808 may receive delivery instructions from theconsignee, via the user computing entity 804 and the central computingentity 802, indicating that the parcel 300 is to be delivered to arestricted access area of the serviceable point 5901. Along with therequest to deliver the parcel to a restricted access area of theserviceable point 5901, the UAV computing entity 804 may receive anaccess code from the consignee (or access the same via the user's userprofile) via the user computing entity 804 and/or the central computingentity 802. The access code may provide selective access to therestricted access area of the serviceable point 5901 (if valid).

In one embodiment, upon receiving a communication of the access codefrom the UAV computing entity 808 (e.g., stored in a user profile), theuser computing entity 804 can validate the access code, and if valid,may command the garage door 5908 (FIG. 58) to open such that the UAV 100may enter and deliver the parcel 300 to the garage 5906 (FIG. 58). Theaccess code may include a unique single-use or temporary access codethat may provide access to the restricted access area of the serviceablepoint 5901 once. For example, upon receiving the unique single-useaccess code from the UAV computing entity 808, the user computing entity804 may validate the access code, and if valid, command the garage door5908 (FIG. 58) to open. In a single-use implementation, the usercomputing entity 804 may not command the garage door 5908 (FIG. 58) toopen upon any subsequent receipt of the unique single-use access code.By utilizing a unique single-use access code, access may be provided fora specific parcel delivery, without providing the UAV computing entity808 or any other computing entity with data/information that might beable to facilitate general access to the restricted access area of theserviceable point 5901.

Furthermore, in some configurations, the access code may include aunique access code that when communicated to the user computing entity804, causes the user computing entity 804 to partially open the garagedoor 5908 (FIG. 58) such that a UAV 100 may navigate to the interior ofthe garage 5906 (FIG. 58). By only partially opening the garage door5908, the access code may allow access to the garage 5908 for deliveryof the parcel 300, without fully opening the garage door 5908 andproviding un-restricted access to the garage 5906 (FIG. 58). While theuser computing entity 804 is described as commanding the garage door5908 to selectively open to allow access to the garage 5906, it shouldbe understood that the user computing entity 804 may selectively provideaccess to any suitable restricted access area of the serviceable point5901.

Alternatively or in addition to receiving and subsequently providing anaccess code to obtain access to the restricted access area of theserviceable point 5901, the UAV computing entity 802 may interactdirectly with the consignee via the user computing entity 804 to obtainaccess to the restricted area of the serviceable point 5901. Forexample, upon arriving to the serviceable point 5901, the UAV computingentity 802 may establish communication with the user computing entity804 (e.g., gate or garage door controller, smart home entity, and/or thelike) and may send a request to access the restricted access area of theserviceable point 5901. The consignee may then provide an input to theuser computing entity 804 that may provide access to the restrictedaccess area of the serviceable point 5901 (e.g., by opening the garagedoor 5908). The UAV computing entity 802 may also close the gate orgarage door in a similar manner. Alternatively, access to the restrictedaccess area may be based on a timer (e.g., the door or gate is open for30 seconds or 1 minute).

The central computing entity 802 may receive a location coordinate(e.g., a latitude and a longitude) of the first desired deliverypoint/location 5902 and the second desired delivery point/location 5904from the consignee via the user computing entity 804 (or access the samevia a corresponding user profile). Alternatively, in some embodiments,upon receiving a request to receive a parcel delivery to the serviceablepoint 5901 from the user computing entity 804, the central computingentity 802 may send the user computing entity 804 information/dataincluding an indicia configured to be printed on a media. As a specificexample, the central computing entity 802 may send a consignee via theuser computing entity 804 a QR code, barcode, MaxiCode, symbol, and/orthe like configured to be printed on a medium and placed at the firstdesired delivery point/location 5902 and/or the second desired deliverypoint/location 5904. The cameras 168 of the UAV 100 may be configured toread the indicia and may utilize the indicia to navigate to the firstdesired delivery point/location 5902 and/or the second desired deliverypoint/location 5904.

Similarly, the central computing entity 802 may receive a locationcoordinate (e.g., a latitude and a longitude) of a desired pick-uppoint/location from the consignee via the user computing entity 804 (oraccess the same via a corresponding user profile). Alternatively, insome embodiments, upon receiving a request to receive a parcel pick-upat the serviceable point 5901 from the user computing entity 804, thecentral computing entity 802 may send the user computing entity 804information/data representing an indicia configured to be printed on amedia. As a specific example, the central computing entity 802 may senda consignee via the user computing entity 804 a QR code, barcode,MaxiCode, symbol, and/or the like configured to be printed on a mediumand placed at the desired pick-up point/location and/or the parcel 300to be picked up. The cameras 168 of the UAV 100 may be configured toread the indicia and may utilize the indicia to navigate to the pick-uppoint/location.

K. Primary and Secondary Pick-Up and Delivery Points

Referring to FIG. 59, one embodiment of operations for delivering aparcel 300 to the serviceable point 5901 is schematically depicted. In afirst step 5802, the UAV 100 navigates to the serviceable point 5901. Asdescribed above, within the serviceable point 5901, a preference fordelivery at the first desired delivery point/location 5902 or thealternate second desired delivery point/location 5904 may be indicatedby the consignee of the parcel 300, such as through the user computingentity 804 or a corresponding user profile. The UAV computing entity 808then proceeds to step 5804, where the UAV computing entity 808determines if the first delivery point/location 5902 (e.g., primarydelivery point) is available for delivery of the parcel 300. If thefirst delivery point/location 5902 is available for delivery of theparcel 300, the UAV computing entity 808 proceeds to step 5808 andnavigates to the first desired delivery point/location 5902. Once theUAV 100 is positioned over the first desired delivery point/location5902, the UAV computing entity 808 proceeds to step 5809 and reduces thepower provided to the propulsion members 102, such that the UAV 100descends to the first delivery point/location 5902. The UAV computingentity 808 may cause the UAV 100 to descend until the ground probe 250is depressed. As described above, the ground probe 250 may becommunicatively coupled to the parcel carrier computing entity 212, anddepression of the ground probe 250 may cause the parcel carrier 200 torelease the parcel 300 at the first desired delivery point/location5902.

If the first delivery point/location 5902 is not available for deliveryof the parcel 300, the UAV computing entity 808 proceeds to step 5810,and the UAV computing entity 808 determines if the second deliverypoint/location 5904 (e.g., secondary delivery point) is available fordelivery of the parcel 300. If the second delivery point/location 5904is not available for delivery of the parcel 300 the UAV computing entity808 proceeds to step S812 and navigates the UAV 100 back to the vehicle10. In the instance that the UAV computing entity 808 navigates the UAV100 back to the vehicle 10 without delivering the parcel 300, the UAVcomputing entity 808 may optionally provide a notification/message tothe user computing entity 804 that the parcel 300 was not successfullydelivered.

If the second delivery point/location 5904 is available for delivery ofthe parcel 300, the UAV computing entity 808 proceeds to step 5814 andnavigates the UAV 100 to the second desired delivery point/location5904. Once the UAV 100 is positioned over the second desired deliverypoint/location 5904, the UAV computing entity 808 proceeds to step 5815and reduces the power provided to the propulsion members 102, such thatthe UAV 100 descends to the second delivery point/location 5904. The UAVcomputing entity 808 may cause the UAV 100 to descend until the groundprobe 250 is depressed. As described above, the ground probe 250 may becommunicatively coupled to the parcel carrier computing entity 212, anddepression of the ground probe 250 may cause the parcel carrier 200 torelease the parcel 300 at the second desired delivery point/location5904.

In embodiments, the UAV computing entity 808 may determine that thefirst delivery point/location 5902 and/or the second deliverypoint/location 5904 are unavailable for delivery of the parcel 300 basedon the detection of objects positioned on or adjacent to the firstdelivery point/location 5902 and/or the second delivery point/location5904 that would prevent the UAV 100 from having a clear route/flightpath to the first delivery point/location 5902 and/or the seconddelivery point/location 5904. For example, the UAV computing entity 808may detect a person near or at the first delivery point/location 5902with the route/flight guidance sensors 166 and/or the one or morecameras 168, such that the UAV 100 may not navigate toward the firstdelivery point/location 5902 without contacting the person. By providinga first delivery point/location 5902 and a second deliverypoint/location 5904, the UAV computing entity 808 may have theopportunity to successfully deliver the parcel 300 to the seconddelivery point/location 5904, instead of returning to the vehicle 10,unsuccessfully delivering the parcel 300. While the operations describedabove with respect to FIG. 59 describe a first delivery point/location5902 and a second delivery point/location 5904, it should be understoodthat the consignee may provide any suitable number of alternate deliverylocations, such as through the user computing entity 804, to which theUAV 100 may attempt to deliver the parcel 300.

L. Pick-Up or Delivery at Restricted Access Area

Referring to FIG. 60, one embodiment of operations for a deliverysequence of the UAV 100 is schematically depicted. In the embodimentdepicted in FIG. 60, the UAV 100 may deliver the parcel 300 to arestricted access area of the serviceable point 5901. In a first step5922, the UAV computing entity 808 may reduce the power provided to thepropulsion members 102 such that the UAV 100 descends to apredetermined/configurable height and positioned apredetermined/configurable distance from the restricted access area ofthe serviceable point 5901. In embodiments, thepredetermined/configurable height and the predetermined/configurabledistance may include any suitable height and distance that allows theUAV computing entity 808 to communicate with the user computing entity804.

In a second step 5924, the UAV computing entity 808 determines ifinstructions were received to deliver the parcel 300 to a restrictedaccess area of the serviceable point 5901. If the UAV computing entity808 did not receive instructions to deliver the parcel 300 to arestricted access area of the serviceable point 5901, the UAV computingentity proceeds to step 5928 and navigates the UAV 100 to the deliverypoint/location at the serviceable point 5901. At step 5929, the UAVcomputing entity 808 may reduce power provided to the propulsion members102, causing the UAV 100 to descend until the ground probe 250 isdepressed. As described above, the ground probe 250 may becommunicatively coupled to the parcel carrier computing entity 212, anddepression of the ground probe 250 may cause the parcel carrier 200 torelease the parcel 300 at the delivery location.

If, at step 5904, the UAV computing entity 808 received instructions todeliver the parcel 300 to a restricted access area of the serviceablepoint 5901, then the UAV computing entity 808 proceeds to step 5926,where the UAV computing entity 808 communicates an access code to theuser computing entity 804. As described above, in response to receipt ofan access code, the user computing entity 804 may selectively provideaccess to the restricted access area of the serviceable point 5901, forexample, by commanding the garage door 5908 (FIG. 58) to open. Aftercommunicating the access code to the user computing entity 804, the UAVcomputing entity 808 proceeds to step 5930 and navigates the UAV to thedelivery point/location within the restricted access area of theserviceable point 5901. At step 5931, the UAV computing entity 808 mayreduce power provided to the propulsion members 102, causing the UAV 100to descend until the ground probe 250 is depressed. As described above,the ground probe 250 may be communicatively coupled to the parcelcarrier computing entity 212, and depression of the ground probe 250 maycause the parcel carrier 200 to release the parcel 300 at the deliverylocation. In this way, the UAV 100 may access restricted access areas ofthe serviceable point 5901 to deliver a parcel 300.

M. Parcel Release Operations at Delivery Point

Reference will now be made to the operations and methods that may beemployed as the parcel 300 is released from the parcel carrier 200.Referring to FIG. 61, one embodiment of operations for a deliverysequence of the UAV 100 is schematically depicted. In a first step 6002,the parcel 300 is released from the parcel carrier 200, for example, inresponse to depression of the ground probe 250. Upon release of theparcel 300 from the parcel carrier 200, the UAV computing entity 808proceeds to step 6004, and receives an indication of the release of theparcel 300 from the parcel carrier 200. For example, the parcel carriercomputing entity 212 may communicate with the UAV computing entity 808and may provide an indication when the parcel 300 is released from theparcel carrier 200. Additionally or alternatively, in some embodiments,the camera 168 of the UAV 100 may record the release of the parcel 300from the parcel carrier 200, via a video and/or still photo.

Upon receiving the indication of the release of the parcel 300 from theparcel carrier 200, the UAV computing entity 808 proceeds to step 6006and communicates confirmation of delivery of the parcel 300 to the usercomputing entity 804 (and/or a variety of other computing entities). Inembodiments where the UAV computing entity 808 records the release ofthe parcel 300 via the camera 168, the UAV computing entity 808 maycommunicate video, still photo, and/or a live video feed of the parcel300 being delivered to the delivery point/location at the serviceablepoint 5901, thereby providing confirmation of delivery of the parcel300, as will be described in greater detail herein. The data/information(e.g., the photos and/or videos) obtained by the camera 168 may beassociated with the parcel 300 and stored at the central computingentity, along with other data/information obtained by the UAV computingentity 808 that may be associated with the parcel 300 and the deliveryvia the UAV 100. For example, telemetry data/information, temperaturedata/information associated with the delivery of the parcel 300 may bestored at the central computing entity 802. The data/informationobtained by the UAV computing entity 808 may subsequently be accessed byother computing entities, such as the user computing entity 804.

In some embodiments, the UAV computing entity 808 may additionally sendan indication to the user computing entity 804 to prompt the consigneeto provide an input confirming the delivery of the parcel 300. The UAVcomputing entity 808 may send the prompt to the user computing entity804 in any suitable manner, and may interface with any suitableplatform, including but not limited to ring.com and/or the like.

At step 6008, the UAV computing entity 808 may optionally communicate anindication and/or an access code to the user computing entity 804 afterleaving the delivery location, for example when the UAV 100 isdelivering a parcel 300 to an access restricted area of the serviceablepoint 5901. Upon receipt of the indication and/or access code, the usercomputing entity 804 may selectively prevent access to the accessrestricted area of the serviceable point 5901, for example, by closingthe garage door 5908. At step 6010, the UAV computing entity 808navigates the UAV 100 back to the vehicle 10.

N. Parcel Pick-Up Operations at Pick-Up Point

Referring to FIG. 62, one embodiment of operations for picking up aparcel 300 at a serviceable point 5901 is schematically depicted. Asdescribed above, the UAV 100 may be dispatched from the vehicle 10 todeliver a parcel 300 from the vehicle 10 to a serviceable point 5901, orthe UAV 100 may be dispatched from the vehicle 10 to pick up a parcel300 from the serviceable point 5901 and return the parcel 300 to thevehicle.

In a first step 6102, the UAV computing entity 808 navigates the UAV 100to a pick-up point/location at the serviceable point 5901. As describedabove, a consignee may request the pick-up of a parcel 300 at theserviceable point 5901 and may provide the UAV computing entity 808 witha pick-up point/location for the parcel 300. Upon arriving at thepick-up point/location at the serviceable point 5901, the UAV computingentity 808 proceeds to step 6104 and reduces the power to the propulsionmembers 102 to descend the UAV 100 to a predetermined/configurableheight at the pick-up point/location at the serviceable point 5901. Inembodiments, the predetermined/configurable height may be any suitableheight at which the camera 168 of the UAV may detect a parcel 300 at thepick-up point/location at the serviceable point 5901.

At step 6106, the UAV computing entity 808 determines if a parcel 300 isdetected at the pick-up point/location at the serviceable point 5901 bythe camera 168. If no parcel 300 is detected at the pick-uppoint/location at the serviceable point 5901, the UAV computing entity808 proceeds to step 6108 and navigates the UAV 100 back to the vehicle10. The UAV computing entity 808 may also provide an indication to theuser computing entity 804 that the UAV 100 did not successfully pick upa parcel from the pick-up point/location.

If a parcel 300 is detected at the pick-up point/location at theserviceable point 5901, the UAV computing entity 808 proceeds to step6110 and causes the UAV 100 to descend over the parcel 300, such as byreducing the power provided to the propulsion members 102. Inembodiments, the UAV computing entity 808 may utilize the camera 168 andthe ground landing sensors 162 to controllably descend over the parcel300 at the pick-up point/location at the serviceable point 5901. In someembodiments, the camera 168 may detect an indicia positioned on theparcel. As the UAV 100 descends, the parcel carrying arms 230 may engagethe parcel 300. For example, as described above, upon the depression ofthe ground probe 250, the parcel carrying arms 230 may move into adisengaged position, such that the parcel carrying arms 230 are spacedapart from the parcel 300. Once the parcel carrying arms 230 arepositioned around the parcel 300, the parcel carrying arms 230 may berepositioned into the engaged position such that the parcel 300 iscoupled to the parcel carrier 200. Once the parcel 300 is coupled to theparcel carrier 200, the parcel carrier computing entity 212 may send asignal to the UAV computing entity 808 indicating that the parcel 300 iscoupled to the parcel carrier 200.

Once the parcel 300 is coupled to the parcel carrier 200, the UAVcomputing entity 808 proceeds to step 6112 and may command power to beprovided to the propulsion members 102 and the UAV computing entity 808navigates the UAV 100 back to the vehicle 10. In embodiments where theUAV 100 automatically picks up a parcel 300 from the pick-uppoint/location (e.g., picks up the parcel 300 without requiring userintervention), the parcel 300 may be of a predetermined/configurablesize/dimension, such that the parcel carrier may accurately engage theparcel 300.

The UAV computing entity 808 may additionally provide anotification/message to the user computing entity 804 that the parcel300 was picked up from the serviceable point 5901. In embodiments wherethe UAV computing entity 808 records the pick-up of the parcel 300 viathe camera 168, the UAV computing entity 808 may communicate video,still photo, and/or a live video feed of the parcel 300 being picked upat the serviceable point 5901, thereby providing confirmation ofdelivery of the parcel 300. The data/information (e.g., the photosand/or videos) obtained by the camera 168 may be associated with theparcel 300 and stored at the central computing entity 802, along withother data/information obtained by the UAV computing entity 808 that maybe associated with the parcel 300 and the pick-up via the UAV 100. Forexample, telemetry data/information, temperature data/informationassociated with the pick-up of the parcel 300 may be stored at thecentral computing entity 802. The data/information obtained by the UAVcomputing entity 808 may subsequently be accessed by other computingentities, such as the user computing entity 804.

O. Additional Parcel Pick-Up Operations at Pick-Up Point

Referring to FIG. 63, one embodiment of operations for picking up aparcel 300 at a serviceable point 5901 is schematically depicted. In afirst step 6202, the UAV computing entity 808 navigates the UAV 100 to apick-up point/location at the serviceable point 5901. As describedabove, a consignee may request the pick-up of a parcel 300 at theserviceable point 5901 and may provide the UAV computing entity 808 witha pick-up point/location for the parcel 300. Upon arriving at thepick-up point/location at the serviceable point 5901, the UAV computingentity 808 proceeds to step 6204 and lands at the pick-up point/locationat the serviceable point 5901, such as by reducing the power provided tothe propulsion members 102. The UAV computing entity 808 may communicatewith the ground landing sensors 162 to controllably land the UAV 100 atthe pick-up point/location at the serviceable point 5901. Upon landingthe UAV 100 at the pick-up point/location at the serviceable point 5901,the UAV computing entity 808 may cease providing power to the propulsionmembers 102 (e.g., causing the propulsion members 102 to stop rotating).The UAV 100 may remain at the pick-up point/location at the serviceablepoint 5901 allowing a user to couple a parcel 300 to the parcel carrier200 of the UAV 100. For example, in embodiments where the parcel carrier200 is coupled to a parcel housing 360 (FIG. 19), the UAV 100 may remainat the pick-up point/location at the serviceable point 5901 allowing auser to place a parcel 300 within the parcel housing 360.

At step 6206, the UAV computing entity 808 and/or the central computingentity 802 receive an indication from the user computing entity 804indicating that the parcel 300 is loaded to the parcel carrier 200. Forexample, the user may provide an input to the user computing entity 804indicating that the parcel 300 is loaded to the parcel carrier 200, andthe user computing entity 804 may communicate the indication to the UAVcomputing entity 804 and/or the central computing entity 802. Uponreceiving the indication that the parcel 300 is loaded to the parcelcarrier 200, the UAV computing entity 804 proceeds to step 6208 anddetermines if a vehicle 10 is positioned within apredetermined/configurable distance of the UAV 100. For example, the UAVcomputing entity 804 may communicate with the central computing entity802 and/or one or more delivery vehicle computing entities 810 todetermine if any vehicles 10 are positioned within apredetermined/configurable distance of the UAV 100. If no vehicles 10are positioned within the predetermined/configurable distance of the UAVcomputing entity 808 will remain at step 6206 and the UAV 100 willremain at the pick-up point/location at the serviceable point 5901. If avehicle 10 is positioned within the predetermined/configurable distanceof the UAV 100, the UAV computing entity 808 proceeds to step 6210 andengages the propulsion members 102 and navigates to the vehicle 10.

In embodiments, the predetermined/configurable distance between the UAV100 and the vehicle 10 may be an estimated route/flight range of the UAV100 based on available power to the UAV 100, such as from the powersupply 214. Once the central computing entity 802 and/or the UAVcomputing entity 808 receive the indication that the parcel 300 isloaded to the parcel carrier, if no vehicle 10 is positioned within thepredetermined/configurable distance of the UAV 100 or if no vehicle isscheduled to be positioned within the predetermined/configurabledistance of the UAV 100, the central computing entity 802 may generateinstructions to dispatch a vehicle 10 to retrieve the UAV 100, or mayre-route a vehicle 10's delivery route/flight such that a vehicle 10will be positioned within the predetermined/configurable distance of theUAV 100, such that the parcel 300 may be retrieved from the pick-uppoint/location.

P. Communication-Based Pick-Up and Delivery Confirmations

In embodiments, the computing entities may send and receive variousnotifications/messages and/or data/information related to the pick-upand/or delivery of parcels 300. As will be recognized, certaincommunication technologies and protocols have range limitations fordirectly connecting to and/or directly communicating with computingentities (e.g., point-to-point, peer-to-peer, Wi-Fi, WLAN, WPAN, and/orthe like). For example, NFC technologies may have range limitations ofless than 12 inches. Various Bluetooth technologies may have rangelimitations from 20 feet to 300 feet. Wi-Fi Direct may have rangelimitations of 600 feet. Thus, depending on the application or context,various communication technologies and protocols can be used to adapt tovarious needs and circumstances. For instance, NFC, Bluetooth, Wi-FiDirect, and other technologies may be used to provide confirmation thatthe UAV 100 actually visited the serviceable point 5901 for a deliveryor pick-up. As will be recognized, a variety of other approaches andtechniques can be used to adapt to various needs and circumstances.

In one embodiment, the UAV computing entity 808 can confirm delivery orpick-up of a parcel by connecting to and/or communicating withregistered user computing entities 804 (e.g., a user's smartphone, Wi-Finetwork, garage door, Echo, Nest, Home, security system, and/or thelike). For instance, in the Bluetooth context, a user computing entity804 can connect with multiple entities simultaneously with each entitybeing within a 30-foot radius. In essence, Bluetooth (and other) systemscreate personal-area networks (PANs) or piconets that may fill an area,room, or vehicle. To create a connection, communication, session, and/orsimilar words used herein interchangeably between a user computingentity 804 and a UAV computing entity 808, a trusted relationship can beestablished between the entities using credential information/data(e.g., passwords and/or other credentials) that can be stored by eachentity for future connection attempts (e.g., the entities are paired).After computing entities have been paired or credential information/datastored, establishing a connection may begin with a phase called“inquiry” through which a UAV computing entity 808 sends an inquiryrequest to all user computing entities 804 found within its range. Theuser computing entities 804 within range would then receive the queryand reply. The UAV computing entity 808 then synchronizes with thevarious user computing entities 804 within range. Once the computingentities are connected (e.g., a connection is established) orcommunicate, the UAV computing entity 808 can provide instructions tovarious user computing entities (e.g., record the delivery, open orclose the garage door, generate a record of the communication, and/orthe like) and/or provide notifications/messages regarding the same. Aswill be recognized, other communication technologies and protocols(e.g., NFC, Wibree, HomeRF, SWAP, Wi-Fi Direct, and/or the like) can beused in a similar manner in terms of connecting and disconnecting withUAV computing entities 808. That is, the other communicationtechnologies and protocols can communicate with or establish connectionsbetween user computing entities 804 and UAV computing entities 808.

In one embodiment, the central computing entity 802 (and/or a variety ofother computing entities) may perform connection-based monitoringregularly, periodically, continuously, during certain time periods ortime frames, on certain days, upon determining the occurrence of one ormore configurable/determinable triggers/events, combinations thereof,and/or the like. In one embodiment, the central computing entity 802(and/or a variety of other computing entities) may performconnection-based monitoring upon determining the occurrence of one ormore configurable triggers/events, in response to requests, in responseto determinations/identifications, combinations thereof, and/or thelike. For example, the connection-based monitoring can be initiatedusing a variety of different triggers—(a) a designated UAV 100 takingoff or landing; (b) a designated UAV 100 beginning to ascend or descend;(c) a designated UAV 100 releasing a parcel; (d) a designated UAV 100moving into or out of a geofenced area; (e) a designated UAV 100 movinginto a geofenced area; and/or a variety of other triggers/events. Aswill be recognized, a variety of other triggers/events can be used toadapt to various needs and circumstances. If a configurable/determinabletrigger/event is not detected, an appropriate computing entity candetermine/identify whether a configurable time period has begun orended. If the appropriate computing entity determines/identifies thatthe configurable time period has not begun or ended, the appropriatecomputing entity can continue monitoring for configurable/determinabletriggers/events. However, if the appropriate computing entitydetermines/identifies that the configurable time period has begun orended, the appropriate computing entity (e.g., central computing entity802) can continuously monitor whether one or more user computingentities 804 are connected to (e.g., communicating with) one or more UAVcomputing entities 808. The monitoring may continue indefinitely, untilthe occurrence of one or more configurable/determinable triggers/events,until a configurable time period has elapsed, combinations thereof,and/or the like.

Continuing with the above example, a UAV computing entity 808 canautomatically communicate with one or more user computing entities 804(e.g., including garage door controllers). To do so, the user profilefor the user (e.g., associated with the parcel to be delivered) can beaccessed to identify any related user computing entities 804 and thecorresponding connection information/data. Generally, the connectionsbetween one or more user computing entities 804 and/or one or more ofthe UAV computing entities 808 can be attempted by or monitored by anyof a variety of computing entities—including central computing entities802, user computing entities 804, UAV computing entities 808, and/or thelike. Continuing with the above example, an appropriate computing entitymay determine/identify when a user computing entity 804 and a UAVcomputing entity 808 are connected or communicating with one another.For instance, upon descent to a serviceable point 5901, the UAVcomputing entity 808 can monitor for connections to or attempt toconnect to one or more user computing entities 804 associated with theparcel using the information/data previously collected or obtained.

Responsive to connecting with one or more user computing entities 804,the UAV computing entity 808 can indicate or provide an indication ofthe same (e.g., that the UAV computing entity 808 is connected to theuser computing entity 804 for Joseph Brown). The indication may includeentity information/data associated with the corresponding user computingentity 804 and/or UAV computing entity 808, such as the correspondingentity identifiers and names. The indication may also include otherinformation/data, such as the location at which the entities connected(e.g., geocode or GPS samples), the time at which the entitiesconnected, and/or the like. The appropriate computing entity can thenstore the information/data in one more records and/or in associationwith the account, subscription, program, parcel information/data, and/orthe like. The information/data can also be stored in association withtracking information/data for the parcel. This may include storing theelectronic signature from the user's profile in association with theparcel information/data for the parcel. That is, the connection canserve as an electronic signature by the user, and the electronicsignature can then be stored accordingly with the information/data forthe parcel.

The appropriate computing entity can also provide notifications/messagesin accordance with users' notification/message preferences. For example,the central computing entity 802 (and/or UAV computing entity 808) canautomatically provide (e.g., generate, queue, and/or transmit) one ormore notifications/messages based on the configurable/determinableparameters for a give user profile (messages to both consignors and/orconsignees). For example, the central computing entity 802 (and/or otherappropriately configured computing entities) can automatically providethe notifications/messages to the electronic destination addressesregarding parcels that have been picked up or delivered or have beenattempted to be picked up or delivered. As will be recognized, this mayinclude generating, queuing, and/or transmitting an email message to auser's email address, a text message to a user's cellular phone, anotification/message to a designated application, and/or the like basedon the configurable/determinable parameters. As will be recognized, avariety of types of messages can be provided to various electronicdestination addresses in response completing or attempting pick-ups ordeliveries. Such notifications/messages may include links or access toparcel information/data and/or the real time location of the parcel. Thelinks or access to information/data sources may be used to providereal-time location information/data of the corresponding UAV computingentity 808. Such notifications/messages can be provided on a periodic orregular basis and/or in response to certain triggers/events.

Q. Notifications/Messages

In embodiments, various computing entities can providenotifications/messages in accordance with users' notification/messagepreferences (e.g., stored in user profiles). For example, the UAVcomputing entity 808 and/or central computing entity 802 canautomatically provide (e.g., generate, queue, and/or transmit) one ormore notifications/messages based on the configurable/determinableparameters for a give user profile (messages to both consignors and/orconsignees). For example, an appropriate computing entity canautomatically provide the notifications/messages to the electronicdestination addresses regarding parcels that have been picked up ordelivered or have been attempted to be picked up or delivered. As willbe recognized, this may include generating, queuing, and/or transmittingan email message to a user's email address, a text message to a user'scellular phone, a notification/message to a designated application,and/or the like based on the configurable/determinable parameters. Aswill be recognized, a variety of types of messages can be provided tovarious electronic destination addresses in response completing orattempting pick-ups or deliveries. Such notifications/messages mayinclude links or access to parcel information/data and/or the real timelocation of the parcel (e.g., including various maps). The links oraccess to information/data sources may be used to provide real-timelocation information/data of the corresponding UAV computing entity 808.Such notifications/messages can be provided on a periodic or regularbasis and/or in response to certain triggers/events.

For example, as noted above, the UAV computing entity 808 may provide anotification/message to the user computing entity 804 upon releasing aparcel 300 from the parcel carrier 200, and may prompt theconsignor/consignee to confirm delivery of the parcel 300 via the usercomputing entity 804. Additionally, the UAV computing entity 808 mayprovide a notification/message to the user computing entity 804 uponpicking up a parcel 300 at the serviceable point 5901, and may promptthe consignor/consignee to confirm pick-up of the parcel 300 vial theuser computing entity 804. The notifications/messages may include sound,video (including 360° video), GIFs, telemetry information/data, pick-upinformation/data, delivery information/data, environmentalinformation/data, links to information/data, still images captured bythe camera 168, and/or the like.

The UAV computing entity 808 and/or central computing entity 802 maysimilarly provide notifications/messages to the user computing entity804 indicating various progress throughout the delivery process,including a notification/message when the UAV 100 is dispatched from thevehicle 10 and an estimated time of arrival of the UAV 100 to theserviceable point 5901.

R. Return and Landing Operations at Vehicle

Referring to FIG. 64, one embodiment of operations for landing a UAV 100to a vehicle 10 is schematically depicted. As described above, a UAV 100may be dispatched from a vehicle to a delivery point/location or apick-up location, and upon delivery or pick-up of a parcel, the UAV 100returns to the vehicle 10. In a first step 6302, the UAV computingentity 808 navigates the UAV 100 to the vehicle 10. In embodiments, theUAV computing entity 808 may communicate with the delivery vehiclecomputing entity 810 and/or the central computing entity 802 todetermine the location of the vehicle 10 and/or the planned route of thevehicle 10. As the UAV 100 approaches the vehicle 10, the UAV computingentity 808 proceeds to step 6304 and receives a signal from the guidancearray 430 of the UAV support mechanism 400, such as through the camera168 and/or the vehicle landing sensors 164. As described above, theguidance array 430 may include visual indicators 432 and positioningbeacons 434 to assist the UAV 100 in locating the position of theopposing rails 410.

The UAV computing entity 808 then proceeds to step 6306 and navigatesthe UAV 100 to the landing region 404 of the UAV support mechanism 400.In particular, the UAV computing entity 808 may rely on the signal orsignals from the guidance array 430 and the vehicle landing sensors 164.As described above, the vehicle landing sensors 164 may include sensors(e.g., LIDAR) that may accurately detect the position of the opposingrails 410 such that the UAV 100 may accurately engage the opposing rails410 such that the UAV 100 may accurately engage the opposing rails 410,engaging the reduced width portion 115 of the UAV chassis 110 with theopposing rails 410. In particular, the UAV computing entity 808 may flythe UAV 100 to the landing region 440 and proceed along the convergingopposing rails 410 until the reduced width portion 115 contacts theopposing rails 410.

In some embodiments, the UAV computing entity 808 may not land to thevehicle 10 while the vehicle 10 is in motion. In particular, it may bedifficult to accurately detect the position of the opposing rails 410while the vehicle 10 is in motion, and the UAV computing entity 808 maycommand the UAV 100 to navigate and follow the vehicle 10 at apredetermined/configurable distance from the vehicle 10 until thevehicle comes to a stop. In some embodiments, the delivery vehiclecomputing entity 810 may send a signal to the UAV computing entity 808when the vehicle 10 is stopped or parked, such that the UAV computingentity 808 may command the UAV 100 to land to the vehicle 10.

In other embodiments, however, the UAV computing entity 808 may commandthe UAV 100 to land to the vehicle 10 while the vehicle 10 is in motionbased on the detected position of the opposing rails 410 and theexpected future movements of the vehicle based on a predetermineddelivery route of the vehicle 10. For example, when the vehicle 10includes an autonomous vehicle, the delivery vehicle computing entity810 may communicate the expected movements of the vehicle to the UAVcomputing entity 808. For example, the delivery vehicle computing entity810 may communicate the speed of the vehicle 10 to the UAV computingentity 808. In such an embodiment, the UAV computing entity 808 maycalculate an optimal landing speed as an offset from the speed of thevehicle 10. For example, if the vehicle 10 were traveling in the forwarddirection at 10 miles per hour, the UAV computing entity 808 couldadjust its speed and direction of travel to 9 miles per hour in the samedirection as the vehicle 10 (in the vehicle's path). Thus, the UAV 100would engage the opposing rails 410 of the vehicle 10 at a difference of1 mile per hour. This would reduce the risks of damage to the vehicle 10and UAV 100. As will be recognized, the delivery vehicle computingentity 810 and UAV computing entity 808 could be in continuouscommunication to provide and receive real time speed changes of thevehicle 10 until the UAV 100 successful lands and engages with theopposing rails 410 of the vehicle 10. In another embodiment, thedelivery vehicle computing entity 810 may provide a regular orcontinuous stream of speed commands to the UAV computing entity 808indicating the optimal landing speed for engagement with the opposingrails 410 of the vehicle 10. This embodiment does not require the UAVcomputing entity 808 to calculate a speed offset of the vehicle 10. Aswill be recognized, a variety of other approaches and techniques can beused to adapt to various needs and circumstances.

S. Parcel/Parcel Carrier Retrieval Operations at Vehicle

Referring to FIG. 65, one embodiment of operations for retrieving aparcel carrier 200 from a UAV 100 that has landed to the vehicle 10 isschematically depicted. As described above, the delivery vehiclecomputing entity 810 is communicatively coupled to the central computingentity 802, and may be communicatively coupled to the robot processor522 and the conveyor controller 460 of the vehicle 10. In a first step6402, the delivery vehicle computing entity 810 determines if the returnposition sensor 450 b indicates if a UAV 100 is positioned within thereturn region 406. If the delivery vehicle computing entity 810 does notreceive a signal from the return position sensor 450 b indicating theUAV 100 is positioned within the return region 406, the delivery vehiclecomputing entity 810 remains at step 6402. If the delivery vehiclecomputing entity 810 receives a signal from the return position sensor450 b indicating that a UAV 100 is positioned within the return region406, the delivery vehicle computing entity 810 proceeds to step 6404 andcommands the robot 500 to retrieve the parcel carrier 200 (and theassociated parcels 300 in the instance of a UAV 100 returning from apick-up) from the UAV 100.

The delivery vehicle computing entity 810 then proceeds to step 6406 tomove the robot 500 to place the parcel carrier 200/parcel 300 to therack 30 within the vehicle 10. The delivery vehicle computing entity 810may then command the conveyor 440 to move the UAV 100 through thetransport region 407 to the supply region 408, such that the UAV 100 maybe re-supplied with another parcel carrier to perform another deliveryor pick-up.

T. Exemplary Recovery Operations

Referring to FIG. 66, one embodiment of operations for UAV emergencyrecovery is schematically depicted. As may be understood, components ofthe UAV 100 may periodically encounter faults. In a first step 6602, ifthe UAV computing entity 808 does not receive a fault indication fromany of the UAV systems or components (such as the propulsion members102, the power supply 214, etc.), the UAV computing entity 808 remainsat step 6602. If the UAV computing entity 808 does receive a faultindication, the UAV computing entity 808 proceeds to step 6604. At step6604, the UAV computing entity 808 determines if the UAV 100 is capableof returning to the vehicle 10 based on the position of the UAV 100 andthe nature of the fault. If the UAV 100 is capable of returning to thevehicle 10, the UAV computing entity 808 commands the UAV to navigateback to the vehicle 10. If the UAV computing entity 808 determines thatthe UAV 100 is not capable of automatically returning to the vehicle 10,the UAV computing entity 808 proceeds to step 6604. At step 6604, theUAV computing entity 808 communicates with the mobile carrier computingentity 806 and/or the central computing entity 802 to allow manualcontrol of the UAV 100 via the mobile carrier computing entity 806and/or the central computing entity 802. By allowing manual control ofthe UAV 100 via the mobile carrier computing entity 806 and/or thecentral computing entity 802, a user, such as a delivery employee mayguide the UAV 100 to an appropriate landing spot such that the UAV 100may be subsequently retrieved. In some embodiments, when the UAV 100 ismanually controlled vial the mobile carrier computing entity 806 and/orthe central computing entity 802, a video feed of the route/flight ofthe UAV 100, such as may be captured by the one or more cameras 168, maybe provided for display to the mobile carrier computing entity 806and/or the central computing entity 802 to allow a user to operate theUAV 100.

In some embodiments, the UAV 100 may optionally include a parachute orother descent control device that may be deployed when the UAV computingentity 808 receives a fault indication. The parachute or descent controldevice may assist in preventing uncontrolled descent of the UAV 100 ifone or more of the UAV components malfunction. In some embodiments, ifthe UAV computing entity 808 loses contact with the central computingentity 802, the UAV computing entity 808 may navigate the UAV 100 backto a last known coordinate, or a last known location at which the UAVcomputing entity 808 had established communication with the centralcomputing entity 802, and upon arriving at the last known location, theUAV computing entity 808 may attempt to re-establish contact with thecentral computing entity 808.

Reference will now be made to the tracking of various UAVs 100 that mayutilized in delivery processes. As may be understood, a carrier mayutilize multiple UAVs 100 and it may be desirable to maintain records ofroute/flight information/data of the UAVs 100 to assist in planningpreventative maintenance of the UAVs 100, as well as to optimize theutilization and operation of the UAVs 100.

U. Exemplary Information/Data Collection and UAV Servicing

Referring to FIG. 67, one embodiment of data records that may beretained, such as by the central computing entity 802 is schematicallydepicted. Each UAV 100 utilized by a carrier may have a unique UAV ID,by which each of the UAVs 100 may be identified. Each of the UAVcomputing entities 808 may record the route/flight time for eachroute/flight the UAV 100 completes and may transmit these route/flighttimes to the central computing entity 802. This may include recordingthe environmental information/data at during flight operations alongwith the corresponding geo coordinates and various other types ofinformation/data. This type of information/data can be used to providereal time status updates for specific geographic areas. Each of theroute/flight times may be compared against a planned route/flight time,which can be based on the position of the UAV 100 at takeoff withrespect to the serviceable point 5901 to which the UAV 100 isdispatched. By comparing planned route/flight time with actualroute/flight times, route/flight paths along a delivery route may beanalyzed and optimized.

The UAV computing entity 808 and/or the central computing entity 802 mayrecord and retain the number of route/flight hours each UAV 100 performsbetween maintenance intervals, and may record and retain different typesof faults experienced by each UAV 100. By retaining performance recordsof each of the UAVs 100, a carrier may optimize preventative maintenanceof the UAVs 100, and may identify repetitive issues or faults ofdifferent UAVs 100.

6. Conclusion

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. For example, variousembodiments may be configured to associate a plurality of assets with aparticular sort location. In such embodiments, a sort employee may scana plurality of asset identifiers (e.g., sequentially) beforetransporting the plurality of items to a sort location. Thereafter, theplurality of assets may be associated with the proximate sort locationaccording to the features and methods described herein. Therefore, it isto be understood that the inventions are not to be limited to thespecific embodiments disclosed and that modifications and otherembodiments are intended to be included within the scope of the appendedclaims. Although specific terms are employed herein, they are used in ageneric and descriptive sense only and not for purposes of limitation.

1. A primary delivery vehicle configured for delivering parcels via anunmanned aerial vehicle (UAV), the primary delivery vehicle comprising:an interior compartment; a roof panel defining a supply portal, whereinthe interior compartment is accessible through the supply portal; aloading robot positioned within the interior compartment, the loadingrobot comprising a robot controller comprising at least one processorand at least one memory including program code, the at least one memoryand the program code configured to, with the processor, cause theloading robot to at least: engage a parcel carrier; move the parcelcarrier to a supply portal; and engage the parcel carrier with a UAVpositioned above the supply portal.
 2. The vehicle of claim 1, whereinthe loading robot comprises an end effector having clamping membersconfigured to engage the parcel carrier.
 3. The vehicle of claim 2,wherein when engaging the parcel carrier, the loading robot controlleris further configured to move the clamping members from a disengagedposition, in which the clamping members are spaced apart from the parcelcarrier, to an engaged position, in which the clamping members engagethe parcel carrier.
 4. The vehicle of claim 2, wherein the loading robotfurther comprises an upright member movably coupled to the end effector,wherein the upright extends in a vertical direction.
 5. The vehicle ofclaim 4, wherein when moving the parcel carrier to the supply portal,the loading robot controller is further configured to move the endeffector upward in the vertical direction along the upright member. 6.The vehicle of claim 2, wherein the loading robot further comprises anend effector track and wherein the clamping members are movably coupledto the end effector track.
 7. The vehicle of claim 6, wherein prior toengaging the parcel carrier, the loading robot controller is furtherconfigured move the clamping members along the end effector track towardthe parcel carrier.
 8. The vehicle of claim 1, wherein the loading robotis movably coupled to a horizontal track extending along a length of theinterior compartment.
 9. The vehicle of claim 8, wherein prior toengaging the parcel carrier, the loading robot controller is furtherconfigured to move the robot toward the parcel carrier along thehorizontal track.
 10. A primary delivery vehicle configured fordelivering parcels via an unmanned aerial vehicle (UAV), the primarydelivery vehicle comprising: an interior compartment; a roof paneldefining a return portal, wherein the interior compartment is accessiblethrough the return portal; a loading robot positioned within theinterior compartment, the loading robot comprising a robot controllercomprising at least one processor and at least one memory includingprogram code, the at least one memory and the program code configuredto, with the processor, cause the loading robot to at least: engage aparcel carrier coupled to a UAV positioned above the return portal;remove the parcel carrier from a UAV chassis of the UAV; move the parcelcarrier from the return portal to a rack positioned in the interiorcompartment; and engage the parcel carrier with the rack of the interiorcompartment.
 11. The vehicle of claim 10, wherein the loading robotcomprises an end effector having clamping members configured to engagethe parcel carrier.
 12. The vehicle of claim 11, wherein when engagingthe parcel carrier, the loading robot controller is further configuredto move the clamping members from a disengaged position, in which theclamping members are spaced apart from the parcel carrier, to an engagedposition, in which the clamping members engage the parcel carrier. 13.The vehicle of claim 11, wherein the loading robot further comprises anupright member movably coupled to the end effector, wherein the uprightextends in a vertical direction.
 14. The vehicle of claim 13, whereinwhen moving the parcel carrier from the return portal, the loading robotcontroller is further configured to move the end effector downward inthe vertical direction along the upright member.
 15. The vehicle ofclaim 11, wherein the loading robot further comprises an end effectortrack and wherein the clamping members are movably coupled to the endeffector track.
 16. The vehicle of claim 15, wherein prior to engagingthe parcel carrier, the loading robot controller is further configuredmove the clamping members along the end effector track toward the parcelcarrier.
 17. The vehicle of claim 10, wherein the loading robot ismovably coupled to a horizontal track extending along a length of theinterior compartment.
 18. The vehicle of claim 17, wherein prior toengaging the parcel carrier, the loading robot controller is furtherconfigured move the robot toward the return portal along the horizontaltrack.